Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web applications > Administer web applications

Modify the default web container configuration

Overview

A web container handles requests for servlets, JSP files, and other types of files that include server-side code. The web container...

• creates servlet instances
• loads and unloads servlets
• creates and manages request and response objects
• performs other servlet management tasks

The web server plug-ins help supported web servers to pass servlet requests to web containers.

If the property to start servlets during application server 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, application server related calls may not work because all of the application server components might not be ready yet. Once the application server is 'ready for e-business', it is completely ready. If application server related calls fail during Servlet.init method, you can either:

• Start the servlet manually when the server is ready for e-business instead of starting the servlet upon startup
• We can choose not to make application server related calls in the servlet's init method

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

Make the following configuration changes if we have a complex application:

1. In the admin console, click...

   Servers | Server Types | WebSphere application servers | server_name

   | web container settings

   ...and then select one of the following...

   Web container	If web application... Requires a virtual host, other than the default_host Requires servlet caching
   Web container transport chains	To reconfigure HTTP connections.

2. If the application handles special client request loads, to modify your thread pool settings...

   Servers | Server Types | WebSphere application servers | server_name

   Additional Properties | Thread pools

3. If the application requires global settings for internal servlets for WAR files packaged by third-party tools...

   Servers | Server Types | WebSphere application servers | server_name

   | Web Container Settings | Web container | Additional Properties | Custom properties

See also

1. Web container settings
2. Programmatic session cookie configuration collection
3. Web container custom properties
4. Web module deployment settings
5. Context root for web modules settings
6. Environment entries for web modules settings
7. Web container troubleshooting tips
8. Disable servlet pooling: Best practices and considerations
9. JSP specific web container custom properties

Related

Class loaders
Web applications: Resources for learning

+

Search Tips   |   Advanced Search