8.7.3 Tuning parameters for optimizing the operations of the Web application

This section explains how to set up the tuning parameters used for optimizing the operations of a Web application.

Organization of this subsection

(1) Tuning parameter for separating the deployment of the static contents and the Web application
(2) Tuning parameters for caching static contents

(1) Tuning parameter for separating the deployment of the static contents and the Web application

Specify the separation of the deployment of the static contents and the Web application as the parameter of the file that defines the operations of the Web server. The setup locations, files and parameters differ depending on the type of Web server used.

The following table explains the method and location of setup:

Table 8‒39: Tuning parameters for separating the deployment of the static contents and the Web application
Method of setup	Location of setup
Smart Composer functionality	Definition file Easy Setup definition file Setup target Logical Web server (`web-server`) Parameter name `manager.web.reverseproxy.mapping`

To Page Top

(2) Tuning parameters for caching static contents

The tuning parameters for cache of static contents are explained below. These tuning parameters are set for each Web container or Web application.

The following table describes how to set up the tuning parameters for each Web container. You specify these items using the Smart Composer functionality.

Table 8‒40: Tuning parameter for caching static contents (items to be set for each Web container)
Setup items	Locations of setup
Select whether static contents cache is to be used	Definition file Easy Setup definition file Setup target Logical J2EE server (`j2ee-server`) Parameter name `webserver.static_content.cache.enabled`
Setup of maximum memory size for each Web application	Definition file Easy Setup definition file Setup target Logical J2EE server (`j2ee-server`) Parameter name `webserver.static_content.cache.size`
Setup of maximum file size of the static contents for cache	Definition file Easy Setup definition file Setup target Logical J2EE server (`j2ee-server`) Parameter name `webserver.static_content.cache.filesize.threshold`

The tuning parameters to be set for each Web application are described below. Set the items in the Web application either directly by editing web.xml or using the server management commands. Edit web.xml for setting the items in the Web application before deployment. You use the server management command (cjsetappprop) for setting the items in the Web application after deployment.

The following table describes the settings:

Table 8‒41: Tuning parameters for caching of static contents (items to be set for each Web application)
Setup items	Settings^#
Select whether to use the cache of static contents	`param-name` tag `com.hitachi.software.web.static_content.cache.enabled` `param-value` tag (Setup value)
Setup of maximum size of memory for each Web application	`param-name` tag `com.hitachi.software.web.static_content.cache.size` `param-value` tag (Setup value)
Setup of maximum file size of the static contents for caching	`param-name` tag `com.hitachi.software.web.static_content.cache.filesize.threshold` `param-value` tag (Setup value)

Note

For details about the values that can be specified in (setup value), see 2.19.2 Definitions in DD (Settings for each Web application) in the uCosminexus Application Server Web Container Functionality Guide.

#

For directly editing web.xml, add <context-param> tag within the <web-app> tag and add the <param-name> and <param-value> tags within the <context-param> tag.

To use the server management commands, add <context-param> tag within the <hitachi-war-property> tag of the WAR property file and add <context-param> and <param-value> tags within the <context-param> tag.

To Page Top