• Certified stack
• Installation
• Deployment
• Security
• Update
• License
• Monitoring
• Setting error pages
• Audit trail
• Languages
• Subscribers
• Tools

System requirements

To run Magnolia within the bundled Tomcat, all you need is a Java SDK, version 1.5 or more recent. Depending on your configuration, a JRE (Java Runtime Environment) will be sufficient; you might need a JDK (Java Development Kit) on some systems.

You can get Java from Sun at http://java.com/getjava or http://java.sun.com/javase/downloads/ for an SDK.

The authoring environment is used through a regular web browser.

Certified stack

See certified stack for a list of software components that have been tested and are guaranteed to work with Magnolia CMS and the Jackrabbit repository.

Known issues

OSX 10.5 - Leopard

If you are using OSX 10.5 or 10.6, you should update to at least 10.5.8 or 10.6.2. Earlier versions cause issues with Magnolia where, when 2 or more instances were started in the same container, some or all connections were dropped. The symptoms are that Tomcat seems unreachable ("kCFErrorDomainCFNetwork:302"), but unfortunately no log message clearly identifies the issue. Sometimes pages could be loaded, but resources couldn't (missing images or stylesheets, ...). Another symptom is that you have to kill Tomcat to stop it (-HUP works), because the shutdown script can't reach the running process either.

You might want to have a look at MAGNOLIA-1959 for more details and/or to comment on your own experience.

Too many open files

On some systems, you won't be able to install/start Magnolia without increasing the maximum amount files that can't be opened at the same time. If you encounter this issues, please see this Wiki page for more details.

Session de-serialization

When installing/updating to a new version, it is possible to encounter such an error message:

2009-11-24 13:02:14,970 ERROR org.apache.catalina.session.ManagerBase : IOException while loading persisted sessions

This can be due to changes in signatures of classes that are stored in the user sessions (such as permissions, user, etc). The error happens when Tomcat attempts to de-serialize serialized sessions, i.e when restarting the container.

The only issue this causes is the loss of persisted sessions (i.e users will have to log in again); it is otherwise completely harmless and can be ignored.

Xalan

Every now and then, someone has a Xalan related issue. If you see the infamous javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found error message in your logs, you'll need to add the Xalan jar to the WEB-INF/lib of your Magnolia instances, delete the repositories and start again. Please see MAGNOLIA-1958 for more details and/or to comment on your own experience.

Which file should I download ?

• magnolia-tomcat-bundle-x.y.z : if you want a standalone version of Magnolia pre-installed in Tomcat with 2 instances (author and public). If you're running with Java 5 or more recent, use of one the -jdk15 variations. If you're stuck with Java 1.4, take one of the -jdk14 variations (they contain the "compatibility package" necessary for Tomcat 5.5 to run with Java 1.4). Usually a .zip file will make Windows users happier, while .tar.gz files will make the day of any Unix or MacOSX user.
• magnolia-bundled-webapp-x.y.z.war : if you want to use Magnolia in your own J2EE container. This war file is pre-installed with the samples and DMS modules. (No workflow)
• magnolia-empty-webapp-x.y.z.war : if you want to build a project on top of Magnolia (where you usually won't want sample content). We recommend to use this artifact as a Maven dependency however. (it is available on our repository)

Additionally, Enterprise Edition users can find the following files:

• magnolia-enterprise-bundle-x.y.z : similar to magnolia-tomcat-bundle-x.y.z, with the additional Enterprise Edition modules.
• magnolia-enterprise-installer-x.y.z : a convenient installer to install the above bundle.
• magnolia-enterprise-webapp-x.y.z.war : similar to magnolia-bundled-webapp-x.y.z.war, with additional Enterprise Edition modules preinstalled.
• Weblogic and WebSphere files : magnolia-enterprise-webapp-x.y.z.war preconfigured for Weblogic 9, Weblogic 10 and WebSphere.

Bundled-webapp vs empty-webapp

In terms of Maven dependencies, custom Magnolia-based webapps should depend on the magnolia-empty-webapp artifact, and add dependencies to the modules they need. The magnolia-bundle project and subprojects are not meant to be used as-is by projects extending Magnolia, but are packaging projects for building Magnolia releases, as a product.