Modifying the default Web container configuration

The Web container is created initially with default properties values suitable for simple web application (.war)s. However, these values might not be appropriate for more complex web application (.war)s.

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

• virtual host

• servlet caching

• special client request loads

• persistent HTTP session support

• special HTTP transport settings

• transaction class mappings

Modify the following properties if you have a complex application:

1. If your web application (.war) requires a virtual host, other than the default_host, or requires servlet caching, modify the Web container General Properties.

2. If your application handles special client request loads, modify the Web Container Additional Properties > Thread Pool setting.

3. If your application requires persistent HTTP session support, modify the Web Container Additional Properties > Session Management setting.

4. If your application requires one of the following HTTP transport settings:

   • Unique hostname and port for client access

   • SSL enablement

   modify the Web Container Additional Properties > HTTP transports setting.

5. If your application requires global settings for internal servlets for WAR files packaged by third-party tools, modify the Web Container Additional Properties > Custom Properties setting.

6. If your application uses transaction class mappings to classify workload, modify the Web Container Additional Properties > Advanced Settings.

 

See Also

Web container
Class loaders
Web container settings
Web Module Deployment settings
Webapplications: Resources for learning

 

---