Was performance tuning

Database Settings

Use this page to specify the settings supported by the database session.

To view this Administration console page, click Servers > server Types > WebSphere application Servers > server_name > Session Management > distributed Environment Settings > database.

The Configuration tab

Data source JNDI Name

Specifies the data source description.

The JNDI name of the data source that is not XA enabled, and the session management feature obtains the database connection from the data source. For example, if the JNDI name of the data source is called "jdbc/sessions", specify "Jdbc/sessions". The data source provides the database connection pool and the configuration of the pool (for example, the pool size). The data source must exist as a configured resource in the environment.

DB2 Row Size

If you use the db2® database, specify the tablespace page size that is configured for the session table. The possible values are 4, 8, 16, or 32,000 kilobytes (KB). The default row size is 4KB.

The default row size is 4KB. In DB2, you can update it to a larger value. In some environments, this can contribute to the performance of the database. When the value is not 4 o'clock, you must specify a tablespace name to use this property. For 4KB pages, the tablespace name is optional.

Table Space Name

Specifies the table space used by the session table.

This value is required when the DB2 page size is not 4 KB.

Use multi-line mode

Specifies that each session data attribute is placed in a separate row in the database, allowing more data to be stored for each session. This operation gains better performance when the session properties are very large and require few changes to the session properties. If using multiline mode is not enabled, instances of application data can be placed in the same row.

Adjust parameter settings

Use this page to set tuning parameters for a distributed session.

To view this Administration console page, click Server > server Types > WebSphere Application Server > server_name > Session Management > distributed Environment Settings > Custom adjustment parameters.

The Configuration tab

Adjustment level

Specifies that the session management facility provides some pre-defined settings that affect performance.

Select a setting from these predefined settings, or customize a setting. To customize the settings, select a predefined setting that is closest to the desired setting, click Customize Settings , make the changes, and then click OK .

TCP Transport Channel Settings Application Server > Server1 > Transport chain > Sipcinbounddefault > TCP Inbound Channel (Tcp_8)

Use this page to configure the TCP inbound channel for inbound network traffic.

Inactivity Timeout

Specifies the amount of time, in seconds, that the TCP transport channel waits for a read or write request on the socket to complete during this time period.

If you do not write the data back to the client in a timely manner before shutting down the client connection, change the inactivity timeout parameter value. This parameter controls the maximum number of connections that can be used by the server. When a new connection is received, the TCP transport channel waits for sufficient data to arrive before dispatching the connection to a protocol-specific channel on the TCP Transport channel. If sufficient data is not received within the time period specified for the inactivity timeout parameter, the TCP transport channel closes the connection.

The default value for this parameter is 60 seconds, which is appropriate for most applications. If the workload involves a large number of connections, and none of these connections can accept the service within 60 seconds, you should increase the value specified for this parameter.

Avoid failure: The value specified for this property can be overwritten by the wait time established by the channel above the channel. For example, the wait time established for an HTTP transport channel overrides the value specified for that property for each operation except for the initial read on the new socket. Thread pool

This field is only available for I5/os and distributed platforms. From the drop-down list of available thread pools, select the thread pool that you want the TCP transport channel to use when dispatching work.

On z/OS platforms, this field does not apply to TCP channels that are members of the WEB container transport chain. These TCP channels work through a special internal thread pool to minimize thread context switching and improve performance.

Exclude Address Lists

Lists the IP addresses that are not allowed to inbound connections.

Use commas to separate the IPv4 and/or IPV6 addresses for which you want to deny access to inbound TCP connection requests.

All four numeric values in a IPV4 address must be represented by a number or wildcard character * (asterisk).

The following is an example of a valid IPV4 address that can be included in the Exclude address list:

*.1.255.0254.*.*.91.*.*.*

Include List of host names

Lists the host names that are allowed for inbound connections. Use a comma to separate the URL addresses that you want to grant access to inbound TCP connection requests.

The URL address can begin with a wildcard character * (an asterisk) followed by a period, for example, *.Rest.Of.Address . If there are no periods after the wildcard character, the asterisk is treated as a regular non-wildcard character. The wildcard character cannot appear anywhere else in the address. For example, it ibm.*.com is not a valid host name.

The following is an example of a valid URL address that can be included in the list of host names:

*.ibm.comwww.ibm.com*.com

Thread Pool Collection

Use this page to view and manage the thread pools used by the application server. The thread pool makes it possible for the server's components to reuse threads, eliminating the need to create new threads at run time. Creating a new thread will consume time and resources.

Note: for z/OS platforms, this page is not available because the thread pool is not used in a z/OS environment. z/OS is an IBM OS

To view this Management console page, you can select multiple navigation paths. For example, click Server > server type > WebSphere Application Server > server > thread pool.

To view the settings for a specific thread pool, click the name of the thread pool.

To create a thread pool, click New , and then enter information on the generated panel.

To delete a thread pool, select the thread pool that you want to delete, and then click Delete .

Was performance tuning