This documentation assumes you understand how your servlet container (e.g. Tomcat or JBoss) works and how to deploy new applications within that container. For purposes of this documentation the directory into which the Imago package was unpacked will be called IMAGO . The next step is to edit the imago.properties and log4j.properties files found in the IMAGO/webapps/imago/WEB-INF directory .

In the imago.properties file you will need to make the following changes:

• Configure the cache manager. The initial setup ships with a memory cache. You will want to verify that the memory settings will work on your system. It may be necessary to provide more heap space to the JVM or reduce the space required.
• If this is a production site you probably want to set errors.internally=false .

In the log4j.properties file you will need to make the following changes:

• Specify a file name for the logging file, e.g. log4j.appended.A1.file=/usr/tomcat/logs/imago.log .
• You may want to enable console logging. To do this comment out the current log4j.rootCategory line and uncomment the one that ends with A2.

Finally:

• Add the required and optional libraries to the classpath or to the servlet classpath.
• add the Imago servlet class org.xenei.imago.Imago to your servlet container configuration.
• Request /imago/index.xml in your browser.
• You should see the Imago Welcome Page.

HEY! I have an error.

The most common error occurs when the JVM places its internal XSLT processor and XML parser before versions required by Imago. The remedy is to either:

• for JVM 1.3.1 and earlier place the xalan.jar and xercesImpl.jar in the JAVA_HOME/lib/ext directory (optionally create symbolic links on UNIX-based systems), or
• for JVM 1.4 and newer place the xalan.jar and xercesImpl.jar in the JAVA_HOME/lib/endorsed directory (optionally create symbolic links on UNIX-based systems), or
• add -Xbootclasspath:IMAGO/webapps/imago/lib/xalan.jar:IMAGO/webapps/imago/lib/xerces.jar to your Java invocation. On Windows systems replace the colon after xalan.jar with a semicolon.

If you still have errors check your logs and configuration. Make sure all required jar files are accessible by the Imago servlet.