To use the functionality for performance tuning, you must specify the settings for the J2EE server, resource adapters, and J2EE applications.
You implement the J2EE server settings with the Easy Setup definition file. Specify the performance tuning definition in the <configuration> tag of the logical J2EE server (j2ee-server) in the Easy Setup definition file.
The following table describes the definition of the functionality for performance tuning in the Easy Setup definition file.
Table 3-53 Definition of the functionality for performance tuning in the Easy Setup definition file
Item | Specified parameters | Settings |
---|---|---|
Enabling connection sharing outside the Application Server-managed transactions | ejbserver.connectionpool.sharingOutsideTransactionScope.enabled | Specifies the connection sharing operations to be performed when connections are obtained multiple times outside the Application Server-managed transactions. |
Connection association | ejbserver.connectionpool.association.enabled | Specifies whether to use the connection association functionality. |
ejbserver.connectionpool.association.enabledDespiteUnshareableSetting | Specifies whether to use the connection association functionality even when non-sharing# of resources is set in the system properties. | |
Statement initialization in the statement pooling functionality | ejbserver.connector.statementpool.clear.backcompat | Specifies the content of the statement to be initialized when a statement is reused in the statement pooling functionality. |
Caching the DataSource objects | ejbserver.jndi.cache.reference | Specifies whether to enable DataSource object caching. |
Optimizing the container-managed sign-on for DB Connector | ejbserver.connectionpool.applicationAuthentication.disabled | Specifies whether to enable the optimization functionality of container-managed sign-on. |
Timeout in error detection | ejbserver.connectionpool.validation.timeout | Specifies the timeout value for the connection error detection functionality and the timeout value for deleting the connections by using the connection count adjustment functionality. |
#: When Unshareable (resources are not share) is specified in the <res-sharing-scope> tag of the WAR property file, Entity Bean property file, Session Bean property file, or Message-driven Bean property file.
For details on the light transaction settings, see 3.4.12 Settings in the execution environment.
Note that the in-process transaction service functionality is used with the default settings. You need not specify the settings.
For details on the Easy Setup Definition file and parameters, see 4.6 Easy Setup Definition file in the uCosminexus Application Server Definition Reference Guide.
Use the server management commands and property files to specify the resource adapter settings in the execution environment. Use the HITACHI Connector Property file to define the functionality for performance tuning.
The following table describes the definition of the functionality for performance tuning in the HITACHI Connector Property file.
Table 3-54 Definition of the functionality for performance tuning in the HITACHI Connector Property file
Category | Items | Specified tags | Settings |
---|---|---|---|
Connection pooling | Minimum and maximum number of connections | MinPoolSize and MaxPoolSize in the <property> tag | Specifies the minimum and maximum number of connections to be pooled in the connection pool. |
Connection pool warming up | Warmup in the <property> tag | Specifies the use of the connection pool warming up functionality. | |
Connection management threads | NetworkFailureTimeout in the <property> tag | Specifies the use of the connection management threads. When you use the connection management threads, a timeout is set for the connection error detection functionality and the connection count adjustment functionality. The timeout value is fixed at 5 seconds with version 07-60 or earlier. With version 08-00 or later, you can specify any timeout value (default value is 5 seconds). | |
Connection count adjustment functionality | ConnectionPoolAdjustmentInterval in the <property> tag | Specifies the interval at which the connection count adjustment functionality will be operated. Note that when a timeout is set for the connection count adjustment functionality, the use of connection management threads is enabled with NetworkFailureTimeout.#1 | |
Statement pooling | Pool size of PreparedStatement#2 | PreparedStatementPoolSize in the <config-property> tag | Specifies the pool size of PreparedStatement. |
Pool size of CallableStatement#2 | CallableStatementPoolSize in the <config-property> tag | Specifies the pool size of CallableStatement. |
#1: The key is the same as that for the timeout in the connection error detection functionality. Therefore, when you use a timeout for the connection error detection functionality, a timeout is also used for the connection count adjustment functionality.
#2: In XDM/RD E2 version 11-01 or earlier, the statement pooling functionality cannot be used; therefore, so specify 0 for these properties.
For details on the HITACHI Connector Property file, see 4.1 HITACHI Connector Property file in the uCosminexus Application Server Application and Resource Definition Reference Guide.
You implement the J2EE application settings in the execution environment using the server management commands and property files. To define the functionality for performance tuning, use the WAR property file, Session Bean property file, Entity Bean property file, or Message-driven Bean property file.
The tags specified in these property files correspond to cosminexus.xml or DD. For details on the definitions in cosminexus.xml, see 3.14.9 Definitions in cosminexus.xml.