Runtime Administration of Web Applications 

Purpose

The Runtime screen of Web Container Service provides information and means of administration of all applications deployed on the J2EE Engine. It contains:

·        Global Web Descriptor
Defines global settings, which are relevant to all web applications running within the Web Container. It is XML based and its DTD is equivalent to that of the web.xml, and the web-j2ee-engine.xml deployment descriptors of the web application.

·        Deployed applications
The components of each web application are described and configured using the web.xml and web-j2ee-engine.xml deployment descriptors. Those configuration settings have greater priority over the global settings of the global-web.xml.

Features

Viewing Web Application Components via Runtime Screen

To view the Global Web Descriptor or to change the deployed web application settings, select the component and choose View.

Displaying Global Web Descriptor and Deployed Web Application

When selecting these components identical screens are displayed, containing information about:

·        Welcome pages, error pages, and response status

·        Tag libraries

·        Mapping servlets and filters

·        References

·        Context parameters

·        MIME mappings

·        Fail over alert messages, limit of sessions count, url rewriting, and cookies configuration

Displaying Servlets and Filters

When selecting a servlet or filter, the displayed screen contains the following information:

·        Name and class of the component

·        Initialization parameters

·        URL Mappings

·        Security settings

Displaying Listeners

When selecting a listener the displayed screen contains the class of the listener. It cannot be changed.

Saving Runtime Changes

When you change a setting in a web application using the Web Container Service Runtime screen, the changes apply to all cluster elements that have this application deployed and running.

You can use the following two options:

·        Choose Save – when you do this in the Runtime screen, the Web Container stops the current application, the changes are applied to all cluster elements, and then the application is started again.

·        Choose Reset – when you this, you discard the changes you have made to the web application’s configuration settings.

Constraints

·        The Web Container runtime administration does not provide functions for adding or deleting a file in the web application. To add or delete a file, you can use the Single File Update function described in Updating a Single File.

·        You cannot change the security settings in the deployed web applications. Using the Runtime screen you can only view them.

If you need to change the security strategy for your web application, you have to redeploy it.

·        You cannot save any changes in the following default servlets loaded from the Global Web Descriptor: jsp, PutServlet, ChangePasswordForm, invoker, and default.

·        You cannot change the session timeout in the Global Web Descriptor. Instead, you can override the default session timeout of 30 minutes by providing a different value for the <session-timeout> tag in the deployment descriptor of your application.