This chapter outlines how to manually deploy Cumulus web applications using WAR files and how to configure an already existing Apache Tomcat Web application server not provided by Canto for Cumulus Web Solutions. Additionally, it provides some hints on trouble shooting and on support for office formats with LibreOffice.
Manual Deployment Using WAR Files
For all Cumulus web applications Canto provides WAR files for manual deployment. Cumulus web applications like Web Client or the publishing portal Cumulus Portals are provided as Java web applications. For execution, the web application must be deployed in a Java servlet container like Apache Tomcat. The servlet container needs access to the Cumulus Java Runtime in order to successfully run the web application.
If you want to manually deploy a Cumulus web application, you can just use the WAR file provided at the same location as the installer files in the Canto Customer Community.
All Cumulus web applications (except Web Server Console) contain a configuration file, by default located in WEB-INF/conf. Make sure to back up the configuration file before replacing the web application to be able to restore it afterwards. You do not need to backup and restore it, if you store the configuration file at another location specified via environment variable. For details see Storing Config Files Outside the Default Location.
Canto strongly recommends you not to employ hot deployment.
2. If required, back up the [web application name]-config.xml configuration file (e.g portals-config.xml) located in WEB-INF/conf folder. If you have customized the log4j.xml file (located in the WEB-INF folder), back up this file as well.
3. Copy the web application’s WAR file into the webapps folder.
4. Delete the web application folder (e.g. portals).
5. Start the Cumulus Web Solutions service/daemon again. (For a detailed description on how to start, see Starting/Stopping Cumulus Web Solutions.) The WAR file will be deployed and a new web application folder is created.
6. If required, copy the saved configuration file into the appropriate folder (by default WEB-INF/conf). (Note that the configuration will be read after a minute; either wait a minute or restart.) And if you have a saved log4j.xml file, copy it in the WEB-INF folder.