3.2.4 Applying tuning for optimizing the number of concurrent executions

This subsection describes the procedure to set the number of concurrent executions for the following main items:

Number of concurrent executions of the Web container and the Web Application unit
- Maximum number of clients that can be concurrently connected
- Number of server processes when starting the Web Server
- Number of concurrent executions of a Web container that processes requests
- Default pending queue size
- Maximum threads in Web container unit
- Default pending queue size
- Concurrent execution count of Stateless Session Beans (Minimum instance value managed in pool)
- Pool minimum value
- Pool maximum value
Concurrent execution count of URL group units
- Maximum threads in Web Application unit
- The number of dedicated threads of the Web application
- Default pending queue size in Web application unit
- Property of a request pending resource watcher in the Web Application unit
- Definition name of the maximum thread number control in URL group unit
- Maximum threads count in URL group unit
- The number of dedicated threads in URL group unit
- Default pending queue size in URL group unit
- URL pattern for controlling URL group unit
- Property for monitoring of the pending requests in URL group unit
  
  Reference note
  
  For details on the reference locations of the windows, commands, and files used in the description, and the storage locations of the commands and files, see 5. Windows, Commands, and Files used in the System Setup and Operations.

Organization of this subsection

(1) Setting the number of concurrent executions in Web container or Web application unit
(2) Setting the number of concurrent executions in URL group unit
(3) Startup and login of the management portal
(4) Changing the settings of J2EE application
(5) Logout from the management portal

(1) Setting the number of concurrent executions in Web container or Web application unit

When a number of concurrent executions in the Web container or Web application is not set, proceed to (2) Setting the number of concurrent executions in URL group unit

Edit cosminexus.xml and store in Any-directory under META-INF directory.

Specify the following in ejb-jar tag in cosminexus.xml.
- Specify session-stateless-pooled-instance-minimum tag (Number of concurrent executions of Stateless Session Bean (Instance minimum value that can be managed in Pool))
In case of multiple session tags specify in each one of them.
Execute jar command by using the command prompt; overwrite cosminexus.xml edited in Step 1 in J2EE application with an archive format.

Command execution example is as follows:
```
jar uvf <File path of MyApp1.ear> -C <Directory in which META-INF directory> <File path of cosminexus.xml under META-INF directory>
```
For File path of MyApp1.ear specify the path of the directory storing J2EE application (MyApp1.ear) and the file name (MyApp1.ear). In the case of the following structure of the cosminexus.xml storage location, Directory in which META-INF directory is placed is set as Any-directory.
```
<Any directory>
     - META-INF
        - cosminexus.xml
```
File path of cosminexus.xml under META-INF directory specifies META-INF directory and file path name (cosminexus.xml) stored in cosminexus.xml in Step 1.
Start the Web browser, connect to http://localhost:28080/mngsvr/index.jsp, and then run the management portal.
Enter "admin" in the management user ID on the Login to Management Server window, and click the Login button.
Click Environment settings of the Logical server on the Management Portal window.
On Server View tab, click DefaultDomain - Logical Web server - Web server - MyWebServer, and then click the Settings tab.
Set the following value in Setting the Web Server window and click the Apply button:
- Server thread (in Windows)
- Concurrent connection client count (In UNIX)
- Number of server processes when starting the server (In UNIX)
The message showing the saving of environment settings appears, and the value is set up.
Click the Back anchor.
On the Server view tab, select DefaultDomain, Logical J2EE server, J2EE server, and MyJ2EEServer, and then click the HTTP Server - Communication and Thread Control tab.
Set the following values in the Settings Related to Communication and Thread Control window, and then click the Apply button.
- Maximum number of connections
- Maximum number of threads
The message showing the saving of environment settings appears, and the value is set up.

Ignore the KEOS19237-W message even if displayed, and go to the next step. This message indicates that the default value (value added automatically by the J2EE server) is used in server-ID-added-to-the-session-ID-of-HttpSession.
Reference note
The KEOS19237-W message will not appear if you set the following value in the Settings Related to Communication and Thread Control window and click Apply button.
- Server-ID-added-to-the-session-ID-of-HttpSession
Click the Deploy Settings anchor.

Reference note

If you want to set additional items, you can return to the Settings Related to Communication and Thread Control window by clicking the Back anchor.
On the Deploy Settings window, insert check mark in Deploy of the logical server having Status as "Blank", and then click the Select and Deploy button.

The Status changes from "Black", to "Deploying", and then to "Deployed".

Reference note

If you click Deploy all button, Settings are re-deployed even on the logical server having the Status as "Deployed".
Click Start/Stop the Logical server on the Management Portal window.
Click DefaultDomain on Server View tab, and then click the Batch run tab.
On Batch Run window click the Execute button.

The request for batch start is received, and the operational status of the logical server in the Operational Status of the Logical Server window changes from "Operating" to "Stopping", to "Stopped", and then to "Operating".
Click Application management of the Logical server on the Management Portal window.
Click DefaultDomain - Logical J2EE server - J2EE server - MyJ2EEServer - Resource - Resource adapter, and then click the Start/Stop tab.
When the Status of Start/Stop of Resource Adapter window is "Operating", click the Stop anchor of Operation.
Click the Yes button on Close the Resource Adapter window.
If "Success" is displayed in the Execution result, click the Back anchor.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of the failure, and then stop the resource adapter again.
Click Property Setting tab and then click the Basic settings anchor of Operation.
On Basic Setting of the Resource Adapter window, click the Setting button.
- Minimum pool value (MinPoolSize)
- Maximum pool value (MaxPoolSize)
Check the message displayed on Basic Settings of Resource Adapter window, and click the Back anchor.

If a message showing failure is displayed, remove the cause of the failure, and then set the property again.
Click the Start/Stop tab, and then click the Start anchor of Operation on Start/stop the Resource Adapter window.
Click the Yes button on Start the Resource Adapter window.
If "Success" is displayed in the Execution result, click the Back anchor.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of the failure, and then start the resource adapter again.

To Page Top

(2) Setting the number of concurrent executions in URL group unit

If you do not want to set the number of concurrent groups per URL, proceed to (3) Startup and login of the management portal.

Edit cosminexus.xml, and store in Any-directory under META-INF directory.

Specify the following in war tag of cosminexus.xml.
- Specify thread-control-thread-control-max-threads tag (maximum threads in Web application unit)
- Specify thread-control-thread-control-exclusive-threads tag (number of dedicated threads of Web application).
- Specify thread-control-thread-control-queue-size tag (pending queue size of Web application unit).
- Specify (Property of a request pending resource watcher in Web Application unit) under thread-control-resource-watcher tag.
- Specify thread-control-urlgroup-thread-control-urlgroup-thread-control-name tag (definition name of number of maximum thread control of URL group unit)
- Specify thread-control-urlgroup-thread-control-urlgroup-thread-control-name tag (maximum thread number control of URL group unit)
- Specify thread-control-urlgroup-thread-control-urlgroup-thread-control-exclusive-threads tag (number of dedicated threads of URL group unit)
- Specify thread-control-urlgroup-thread-control-urlgroup-thread-control-queue-size tag (pending queue size of URL group unit)
- Specify thread-control-urlgroup-thread-control-urlgroup-thread-control-mapping tag (URL pattern controlling URL group unit).
- Specify (property for monitoring pending request count per URL group) under thread-control-urlgroup-thread-control-stats-monitor-waiting-request-count tag
Execute jar command by using the command prompt, set cosminexus.xml edited in Step 1 in J2EE application with an archive format.

Command execution example is as follows:
```
jar uvf <File path of MyApp1.ear> -C <Directory in which META-INF directory> <File path of cosminexus.xml under META-INF directory>
```
For File path of MyApp1.ear specify the path of the directory storing J2EE application (MyApp1.ear), and the file name (MyApp1.ear). In the case of the following structure of cosminexus.xml storage location, Directory in which META-INF directory is placed is set as Any-directory.
```
<Any directory>
    - META-INF
        - cosminexus.xml
```
File path of cosminexus.xml under META-INF directory specifies META-INF directory and file path name (cosminexus.xml) stored in cosminexus.xml in Step 1.

To Page Top

(3) Startup and login of the management portal

Once you have already logged in to management portal, proceed to (4) Changing the settings of J2EE applications.

Start the Web browser, connect to http://localhost:28080/mngsvr/index.jsp, and then run the management portal.
Enter "admin" in the management user ID on the Login to Management Server window, and click the Login button.

To Page Top

(4) Changing the settings of J2EE application

Upload and re-import J2EE Application (MyApp1.ear) recreated by editing cosminexus.xml.

Click Application Management of the Logical server on the Management Portal window.
Click DefaultDomain - Logical J2EE server - J2EE server - MyJ2EEServer - Application, and then click the Start/Stop J2EE application tab.
On the Start/Stop J2EE Application window, click the Stop anchor of Operation for the display name (MyApp) of the applications before replacement in the Import J2EE applications list.
Click the Yes button on Stop J2EE Application window.
Check the Execution result, and click the Back anchor.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of the failure, and then stop again.

When "Success" is displayed in the Execution result, the Status of the Start/Stop J2EE Application window changes to "Stopped".
Click DefaultDomain - Logical J2EE server - J2EE server - MyJ2EEServer - Application, and then click the Delete tab.
In Delete J2EE Application window, click the Delete anchor of Operation for the display name (MyApp) of the applications before replacement in the Import J2EE applications list.
Click the Yes button on Delete J2EE Application window.
Check the Execution result, and click the Back anchor.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of the failure, and then delete J2EE application again.

When "Success" is displayed in the Execution result, the application is deleted from the Import J2EE applications list on Delete J2EE Application window.
Click the DefaultDomain.
Enter "J2EE Application" (MyApp1.ear) re-created in (1) Setting the number of concurrent executions in Web container or Web application unit or (2) Setting the number of concurrent executions in URL group unit in J2EE application file on Upload J2EE Application window, and click the Upload button.
Check the displayed message, and click the Back anchor.

If a message showing failure appears, remove the cause of the failure and upload again.

The file name (MyApp1.ear) of J2EE application uploaded in Step 11 is displayed in the Upload directory files list.
Click DefaultDomain - Logical J2EE server - J2EE server - MyJ2EEServer - Application, and then click the Import tab.
Select the file (MyApp1.ear) uploaded in Step 11 from J2EE application files in Import J2EE Application window and then click the Execute button.
If "Success" is displayed in the Execution result, click the Back anchor.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of the failure, and then import J2EE application again.
Click DefaultDomain - Logical J2EE server - J2EE server - MyJ2EEServer - Application, and then click the Start/Stop tab.
In the Start/Stop J2EE Application window, click the Start anchor of Operation for display name (MYApp) of J2EE applications imported in step 14. in the Import J2EE applications list.
Click the Yes button in the Start J2EE Application window.
Check the Execution result, and click the Back anchor.

If "Failure" is displayed in the Execution result, click the Display log tab, check the message in the Display Log window, remove the cause of failure, and then start the J2EE application again.

If "Success" is displayed in the Execution result, Status of the Start/Stop J2EE Application window changes to "Operating".

To Page Top

(5) Logout from the management portal

Click the Logout anchor.
Check the displayed message, click the Login window, and close the Web browser.

To Page Top