Modifying the default Web container configuration

About this task

A Web container handles requests for servlets, JavaServer Pages (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, and performs other servlet management tasks. The Web server plug-ins, provided by the product, 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 or
  • You can choose not to make application server related calls in the servlet's init method.

The Web container is created initially with default properties values suitable for simple Web applications. However, these values might not be appropriate for more complex Web applications.

Your application is considered complex if it requires any of the following features:

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

Procedure

  1. In the administrative console, click Servers > Server Types > WebSphere application servers > server_name . Then under Web container settings, click on one of the following:
    1. Web container, if your Web application requires a virtual host, other than the default_host, or requires servlet caching.
    2. Web container transport chains, if you need to reconfigure your HTTP connections.
  2. If your application handles special client request loads, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name . Then under Additional Properties, click Thread pools to modify your thread pool settings.
  3. If your application requires global settings for internal servlets for Web archive (WAR) files packaged by third-party tools, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Web Container Settings > Web container . Then under Additional Properties, click Custom properties and enter the appropriate custom property.

What to do next

  • Web container settings

    Use this page to configure the Web container settings.

  • Web container custom properties

    You can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console. The following is a list of some of the available Web container custom properties.

  • Web module deployment settings

    Use this page to configure an instance of Web module deployment.

  • Context root for Web modules settings

    Use this page to specify the context root for Web modules during or after installation of an application onto a WebSphere® Application Server deployment target.

  • Environment entries for Web modules settings

    Use this page to configure the environment entries of Web modules such as servlets and JavaServer Pages (JSP) files.

  • Web container troubleshooting tips

    Learn about ways to troubleshoot Web container.

  • Disabling servlet pooling: Best practices and considerations

    This topic provides usage examples of when you may want to disable servlet pooling. You may want to disable request and response pooling if your application is creating threads inside of the application or if you are concerned about the Web container reusing request and response objects.

  • JavaServer Pages specific Web container custom properties

    You can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. Defining a new property enables you to configure a setting beyond what is available in the administrative console. The following is a list of the available JavaServer Pages custom properties. The JavaServer Pages custom properties are case sensitive.




In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 9:57:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-dist&topic=tweb_aov8
File name: tweb_aov8.html