Tomcat Web Hosting Blog - Java, JSP, EJB, Hibernate

Chapter 8: Web Application Administration As you can see in the figure, the response for a successful command execution (the Messageparameter) is an OK string. A missing OK is an indication of failure, and the rest of the message provides the cause. The possible causes of failure for each command are listed later in this chapter in the section Possible Errors. During installation of Tomcat on Windows, using the installer executable (and not the Zip file), the installer asks the user for the admin username and password. The username and password entered at install time are used to generate entries for the tomcat-users.xmlfile for both the manager and admin Web applications. Hence, no configuration is needed in this case, unless another user with manager privileges is to be added or the manager password is to be changed. Manager Application Configuration The previous section looked at tomcat-users.xml, which defines the username and password for the manager role. The other manager application related configuration parameters are the manager context entry and the deployment descriptor. No changes have to be made for the manager application to work the settings are configured by default. They can, however, be modified for deployment requirements for example, to change the security constraints for the manager application, to change the authentication mechanism for users in the manager role, or even to change the name of the role from manager to some other name if required. This section covers these configurable parameters for the manager application. Manager Application Context Entry In Tomcat 6, unlike Tomcat 5/5.5, the manager context is configured in the same way as the other application contexts. Following is the default configuration for the manager application context from the $CATALINA_HOME/ webapps/manager/META-INF/context.xmlfile: This only difference from a standard web application is the setting of the privileged attribute to true. This enables the application to access the container s servlets. This attribute is false for a normal Web application deployed in Tomcat. In Tomcat 5/5.5, the context was defined in the $CATALINA_HOME/server/webapps/manager/ manager.xmlfile. Manager Application Deployment Descriptor The tomcat-users.xml file shown earlier defined the username and password for the manager role. This section discusses how the security constraints for this role are specified. The manager application s deployment descriptor for versions prior to Tomcat 4.1 is $CATALINA_HOME/webapps/manager/WEB-INF/web .xml. In Tomcat 5, the web.xmlfile moved to $CATALINA_HOME/server/webapps/manager/WEB-INF; however, it is back to the original location under $CATALINA_HOME/webapps/manager/WEB-INF/in Tomcat 6.

For high quality website hosting services please check tomcat web hosting website.

This entry was posted on Saturday, April 25th, 2009 at 11:34 pm and is filed under tomcat. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.