Web container settings

Specifies a virtual host that enables a single host machine to resemble multiple host machines. Resources that are associated with one virtual host cannot share data with resources that are associated with another virtual host, even if the virtual hosts share the same physical machine.

Select a virtual host option:

default_host

The product provides a default virtual host with some common aliases such as the machine IP address, short host name, and fully qualified host name. The alias comprises the first part of the path for accessing a resource such as a servlet. For example, it is localhost:9080 in the request http://localhost:9080/myServlet.

admin_host

This virtual host option is another name for the application server; also known as server1 in the base installation. This process supports the use of the administrative console.

proxy_host

The virtual host called proxy_host, includes default port definitions, port 80 and 443, which are typically initialized as part of the proxy server initialization. Use this proxy host as appropriate with routing rules associated with the proxy server.

Specifies that if a servlet is started and it generates output to be cached, a cache entry is created containing not only the output, but also side effects of the invocation. These side effects can include calls to other servlets or JavaServer Pages (JSP) files and metadata about the entry, including timeout and entry priority information.

Portlet fragment caching requires that servlet caching is enabled. Therefore, enabling portlet fragment caching automatically enables servlet caching. Disabling servlet caching automatically disables portlet fragment caching.

Specifies to disable the pooling of servlet request and servlet response objects that are pooled by the web container. When you disable pooling of servlet request and servlet response objects, new servlet request and servlet response objects are created for each request.

When you disable pooling of servlet request and servlet response objects, new servlet request and servlet response objects are created for each request, which can negatively affect performance, but provides protection from any unforeseen pooling bugs.

Specifies to gather information about applications deployed on the server and make it available as Swagger documents.

The API discovery service enables you to find REST APIs within the server. You can get a Swagger document with information about the REST APIs.

Specifies the number of threads that are available to handle asynchronous servlet timeout operations per server.

The default of two might be too low if you have many applications using asynchronous servlets that often have timeouts.

Specifies the default asynchronous servlet timeout for the server.

The default of 30 seconds can be lowered if responses are not being received quickly enough and there is a viable fall back in the error case. You can raise the value if too many timeouts are being received and the longer timeout produces responses in an acceptable manner to the client. The units are in millisecond, so multiply the number by 1000 to convert to seconds. To configure at a higher granularity, you must use the AsyncContext setTimeout method programmatically.

Select this option to use a work manager to start the runnable. This option is the default selection. The work manager option propagates any context that is configured for the selected work manager. This option also requires selecting the JNDI name of the work manager that you use.