Web Container Service
Purpose
The Web Container Service is an implementation of a container of J2EE Web components. It complies with Java Servlet 2.3 Specification and JavaServer Pages 1.2 Specification. This implies that the J2EE Engine’s Web Container observes certain J2EE standards and provides all functions required by these standards.
The most important function of the Web Container Service is to enable the life cycle management of Web applications. It also helps developing and running session- and security-aware Web applications.
Integration
The Web Container Service is based on the communication infrastructure of the HTTP Provider Service. The first one manages J2EE Web components across a cluster environment, generates dynamic responses, and so on. The second service is used to deliver requests and transfer response data back to the client.
The Web Container
Service has a strong reference to the HTTP Provider Service. This is, if HTTP
Provider Service stops for some reason, the Java Enterprise Runtime stops the
Web Container Service as well. For more information about references between
server components, see
Components
References in the Architecture Manual.
Features
All tasks of the Web Container Service are performed using the Visual Administrator tool.
· Specifying Compilation Time of JavaServer Pages
· Specifying Servlet Execution Destroy Timeout
· Configuring the Header Preventing Dynamic Responses Compression
· Configuring the Name of the Multipart Body Request Attribute
· Delaying User Authentication
· Providing Custom Response Messages When Requesting Stopped Applications
· Isolating Running Web Applications from Productive Client Requests
· Enable and Configure Tracing for Web Applications
· Runtime Administration of Web Applications
Using Telnet you can list the HTTP sessions and the security policy domains in all running applications of the Web Container. For more information about the Web Container Service shell commands available, see SERVLET_JSP.