Using Apache Tomcat on dedicated host
for FirstSpirit WebApps
This addendum complements:
PDF: FirstSpirit Manual for Administrators
Chapters: 4.5.4 Tomcat servlet engine on a dedicated host
Problem:
Tomcat is configured according to chapter 4.5.4 to enable automatic deployment of the FirstSpirit WebApps fs5root, fs5webmon, fs5webedit, fs5preview via the Tomcat Manager webservice but the WebApps cannot be enabled in FirstSpirit or are not available on the Tomcat webserver.
Solution:
The Tomcat Manager WebApp is required for the automatic deployment process of the FirstSpirit WebApps fs5root, fs5webmon, fs5webedit, fs5preview. For Tomcat since 6.0.30 and Tomcat 7 a technical user with role manager-script must be enabled in tomcat/conf/tomcat-users.xml. The role manager-gui is not required for FirstSpirit, but it is useful for manual configuration and status check of the Tomcat server. On older Tomcat 6 version before 6.0.30, the role manager-gui has to be used instead of manager-script.
The configuration property Tomcat Manager URL within the FirstSpirit ServerManager (AdminClient) in section Server Properties -> WebServers must be set to the following entry:
Tomcat 6: http://tomcathost:8080/manager
Tomcat 7: http://tomcathost:8080/manager/text
While installing and enabling each WebApp, check for error messages in firstspirit5/log/fs-server.log.
