Table of Contents
You will need to deploy the server component and the portlets separately. Please note that however we listed recommended container implementations below, you can use any other product until that is compliant with the appropriate servlet or portlet specifications. You can learn more about the compatibity issues by studying the compatibility matrix maintained on the project website.
We offer deployment scripts in form of Ant build
scripts, which automatize the deployment process. If you
want to use these, you will need to install Ant.
The default target of each script is redeploy
,
which deletes the old deployment (if there exists) and deploys a
new clean one.
Of course, you can still deploy manually if Ant is not available in your environment. Even in this case, it's a good idea to look through the deploy scripts and then to follow the step-by-step guide provided in the next sections.
The server component requires standard servlet containers (or a single container) for proper running. The most trivial option is to use the Apache Tomcat container.
The portlets needs a JSR-168-compliant portlet container. One possible open source choice is JBoss Portal deployed into a JBoss Application server instance.
For storing the dynamically generated content (e.g. chart images), you need a WebDAV server implementation. One option is to use Jakarta Slide, but Subversion provides a WebDAV interface, too.