I.2 Effective parameters deployed by abstract parameters

When you execute the cmx_trans_param command for the maximum number of concurrently processed requests that is the abstract parameter, the value will be deployed to the following seven effective parameters in the Easy Setup definition file:

ThreadsPerChild
MaxClients
StartServers
HWSKeepStartServers
KeepAliveTimeout
webserver.connector.ajp13.backlog
webserver.connector.ajp13.max_threads

Additionally, you can use this abstract parameter to determine values of the following two parameters in the Connector property file. Note that the Connector property file is used for acquiring and editing resource adapter attributes.

MaxPoolSize
MinPoolSize

This subsection describes the rules for deploying effective parameters in the Easy Setup definition file and the rules for specifying the values of parameters that are set in the Connector property file.

Organization of this subsection

(1) Effective parameters deployed in the Easy Setup definition file
(2) Example of abstract parameter deployment
(3) Parameter values in the Connector property file

(1) Effective parameters deployed in the Easy Setup definition file

This subsection describes the rules for each effective parameter when deploying values of maximum number of concurrently processed requests in each effective parameter and also describes the effective parameter. Note that Setup destination file in the description indicates the Cosminexus file in which the information of the Easy Setup definition file with the deployed abstract parameter is finally applied.

(a) ThreadsPerChild

Deployment rules

(KeepAliveTimeout + average-processing-time-per-request) / average-processing-time-per-request × maximum-number-of-concurrently-processed-requests

The deployment rule is as described above, and the calculation is as follows: average-processing-time-per-request = KeepAliveTimeout

Therefore, the formula is as follows:

maximum-number-of-concurrently-processed-requests × 2

Description related to the effective parameter

This parameter specifies the number of threads to be started as the Web server, using Cosminexus HTTP Server. The specified thread count indicates the maximum number of concurrent connections of the Web server.

For details, see the uCosminexus Application Server HTTP Server User Guide.

Setup destination file

httpsd.conf (Cosminexus HTTP Server definition file)

(b) MaxClients

Deployment rules

(KeepAliveTimeout + average-processing-time-per-request) / average-processing-time-per-request × maximum-number-of-concurrently-processed-requests

The deployment rule is as described above, and the calculation is as follows: average-processing-time-per-request = KeepAliveTimeout

Therefore, the formula is as follows:

maximum-number-of-concurrently-processed-requests × 2

Description related to the effective parameter

This parameter specifies the maximum number of clients that can connect concurrently with Cosminexus HTTP Server.

Setup destination file

httpsd.conf (Cosminexus HTTP Server definition file)

(c) StartServers

Deployment rules

(KeepAliveTimeout + average-processing-time-per-request) / average-processing-time-per-request × maximum-number-of-concurrently-processed-requests

The deployment rule is as described above, and the calculation is as follows: average-processing-time-per-request = KeepAliveTimeout

Therefore, the formula is as follows:

maximum-number-of-concurrently-processed-requests × 2

Description about the effective parameter

This parameter specifies the number of server processes used for starting the Web server, using Cosminexus HTTP Server.

For details, see the uCosminexus Application Server HTTP Server User Guide.

Setup destination file

httpsd.conf (Cosminexus HTTP Server definition file)

(d) HWSKeepStartServers

Deployment rules: On is deployed.
Description about the effective parameter: This parameter specifies whether the number of running server processes will be maintained at the number specified in the StartServers parameter by using Cosminexus HTTP Server. For details, see the uCosminexus Application Server HTTP Server User Guide.
Setup destination file: httpsd.conf (Cosminexus HTTP Server definition file)

(e) KeepAliveTimeout

Deployment rules

3 (Seconds) is deployed.

Description about the effective parameter

This parameter specifies the time for which the connection is maintained for KeepAliveTimeout, when HTTP 1.1 persistent connection is established.

When a persistent connection is used (when the KeepAlive directive is set to On) for a faster response, the connection is not broken even after a response is returned for the client request and the system waits for the next request from the same client. Therefore, you specify a timeout value for KeepAliveTimeout.

For details, see the uCosminexus Application Server HTTP Server User Guide.

Setup destination file

httpsd.conf (Cosminexus HTTP Server definition file)

(f) webserver.connector.ajp13.backlog

Deployment rules

(KeepAliveTimeout + average-processing-time-per-request) / average-processing-time-per-request × maximum-number-of-concurrently-processed-requests

The deployment rule is as described above, and the calculation is as follows: average-processing-time-per-request = KeepAliveTimeout

Therefore, the formula is as follows:

maximum-number-of-concurrently-processed-requests × 2

Description about the effective parameter

This parameter specifies the maximum number of pending matrix for the connection requests from the redirector.

Setup destination file

usrconf.properties (User property file for J2EE server)

(g) webserver.connector.ajp13.max_threads

Deployment rules: maximum-number-of-concurrently-processed-requests is deployed as it is.
Description about the effective parameter: This parameter specifies the number of requests processed concurrently by the Web container.
Setup destination file: usrconf.properties (User property file for J2EE server)

To Page Top

(2) Example of abstract parameter deployment

When you execute the cmx_trans_param command, the parameters listed in the following table are automatically deployed within the <configuration> tag of the physical tier definition (definition of the <tier> tag), and the Easy Setup definition file with the deployed abstract parameter is created:

Table I‒1: List of parameters automatically deployed using the cmx_trans_param command
logical-server-type	param-name
`web-server`	`ThreadsPerChild`
	`MaxClients`
	`StartServers`
	`HWSKeepStartServers`
	`KeepAliveTimeout`
`j2ee-server`	`webserver.connector.ajp13.backlog`
`j2ee-server`	`webserver.connector.ajp13.max_threads`

For details on the parameters, see 4. Files Used by the Smart Composer Functionality in the uCosminexus Application Server Definition Reference Guide.

The contents of the Easy Setup definition file with the deployed abstract parameter are as follows (excerpt):

Easy Setup definition file with the deployed abstract parameter

<?xml version="1.0" encoding="UTF-8"?>
<model-definition xmlns="http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5">
 <web-system>
 <name>MyWebSystem</name>
 <!-- definition-of-the-load-balancer -->
 <load-balancer>
  :
 </load-balancer>
 <!-- definition-of-physical-tier-(combined-tier) -->
 <tier>
  <tier-type>combined-tier</tier-type>
 
  <!-- Generate web-server configuration by cmx_trans_param -->
  <configuration>
  <logical-server-type>web-server</logical-server-type>
  <param>
   <param-name>ThreadsPerChild</param-name>
   <param-value>40</param-value>
  </param>
  <param>
   <param-name>MaxClients</param-name>
   <param-value>40</param-value>
  </param>
  <param>
   <param-name>StartServers</param-name>
   <param-value>40</param-value>
  </param>
  <param>
   <param-name>HWSKeepStartServers</param-name>
   <param-value>On</param-value>
  </param>
  <param>
   <param-name>KeepAliveTimeout</param-name>
   <param-value>3</param-value>
  </param>
  </configuration>
 
  <!-- Generate j2ee-server configuration by cmx_trans_param -->
  <configuration>
  <logical-server-type>j2ee-server</logical-server-type>
  <param>
   <param-name>webserver.connector.ajp13.backlog</param-name>
   <param-value>40</param-value>
  </param>
  <param>
   <param-name>webserver.connector.ajp13.max_threads</param-name>
   <param-value>20</param-value>
  </param>
   ...
  </configuration>
 </tier>
 <!-- definition-of-service-unit -->
 <unit>
  ...
 </unit>
 </web-system>
 <!-- definition-of-host -->
 <host>
 ...
 </host>
</model-definition>

Note: Definitions that have been automatically expanded are indicated in bold type with a background color.

To Page Top

(3) Parameter values in the Connector property file

You can determine the settings for the MaxPoolSize and MinPoolSize parameters in the Connector property file on the basis of the value of the abstract parameter. The parameters are not automatically set using the cmx_trans_param command. You manually specify the parameters in the Connector property file, and then deploy resource adapters.

(a) MaxPoolSize

Set value: Specifies the value set in maximum-number-of-concurrently-processed-requests.
Description about the effective parameter: This parameter specifies the maximum value of the connection pool.
Setup destination file: Connector property file

(b) MinPoolSize

Set value: Specifies the value set in maximum-number-of-concurrently-processed-requests.
Description about the effective parameter: This parameter specifies the minimum value of the connection pool.
Setup destination file: Connector property file

To Page Top