Modify the default Web container configuration
The Web container...
- creates servlet instances
- loads and unloads servlets
- creates and manages request and response objects
- and performs other servlet management tasks
The Web server plug-ins, provided by WAS ND, help supported Web servers to pass servlet requests to Web containers.
If the property to start servlets during appserver startup is enabled, part of its startup process calls the Servlet.init method on its servlets when you start the Web container. Therefore, when the Web container starts and calls the init method, other components such as Naming and Work Load Management might not be fully started yet. As a result, appserver related calls may not work because all of the appserver components might not be ready yet.
Once the appserver is...
ready for e-business...it is completely ready.
If appserver related calls fail during Servlet.init method, we can either:
- Start the servlet manually when the server is ready for e-business instead of starting the servlet upon startup or
- We can choose not to make appserver related calls in the servlet's init method.
The Web container is created initially with default properties values suitable for simple Web apps. However, these values might not be appropriate for more complex Web apps.
Your application is considered complex if it requires any of the following features:
- Additional virtual host aliases
- Servlet caching
- Persistent HTTP session support
- Session tracking support with URL rewriting
- Special Web container transport chain settings
- Asynchronous or remote dispatching
- No request or response pooling
If we have a complex application...
- In the admin console, click...
Servers | Server Types | WebSphere application servers | server_name | Web container settings
- Click on one of the following:
- Web container
If the Web app requires a virtual host, other than the default_host, or requires servlet caching.
- Web container transport chains
To reconfigure the HTTP connections.
- If the application handles special client request loads, to modify the thread pool settings...
Servers | Server Types | WebSphere application servers | server_name | Additional Properties | Thread pools
- If the application requires global settings for internal servlets for WAR files packaged by third-party tools, click...
Servers | Server Types | WebSphere application servers | server_name | Web Container Settings | Web container | Additional Properties | Custom properties
- Enter the appropriate custom property.
Web container settings
Web container custom properties
Web module deployment settings
Context root for Web modules settings
Environment entries for Web modules settings
Web container troubleshooting tips
Disable servlet pooling: Best practices and considerations
Related concepts
Class loaders
Related
Web apps: Links