For connections to DB2® for Linux, UNIX, and Windows data servers in a DB2 pureScale® instance, connection-level workload balancing is enabled at a non-Java client by default. Transaction-level workload balancing capability must be enabled explicitly.
The following table describes the basic settings to enable connection-level workload balancing support for non-Java™ applications.
Client setting | Value |
---|---|
Connection address: | |
database host1 | The IP address of a member of a DB2 pureScale instance.2 |
database port1 | The SQL port number of a member of a DB2 pureScale instance2 |
database name1 | The database name |
Note:
|
You can use the following configuration keyword in the db2dsdriver.cfg file to change the connection-level workload balance setting.
Element in the db2dsdriver.cfg configuration file | Section | Value |
---|---|---|
connectionLevelLoadBalancing parameter | <database> | Specifies whether connection-level load balancing is in effect. The value is true by default. |
You can use the following configuration keywords in the db2dsdriver.cfg file to enable and fine-tune transaction-level workload balancing.
Element in the db2dsdriver.cfg configuration file | Section | Value |
---|---|---|
connectionLevelLoadBalancing parameter | <database> | Must be set to true if you want to use transaction-level workload balancing. The setting is true by default. |
enableWLB parameter | <wlb> | Specifies whether transaction-level workload balancing is in effect. The value is false by default. |
maxTransportIdleTime | <wlb> | Specifies the maximum elapsed time in number of seconds before an idle transport is dropped. The default is 60 . The minimum value is 0. |
maxTransportWaitTime | <wlb> | Specifies the number of seconds that the client waits for a transport to become available. The default is 1 . The minimum supported value is 0, and -1 specifies unlimited time. |
maxTransports | <wlb> | Specifies the maximum number of physical connections that can be made for each application process that connects to the DB2 pureScale instance. The default is -1 (unlimited) . |
maxRefreshInterval | <wlb> | Specifies the maximum elapsed time in number of seconds before the server list is refreshed. The default is 10. The minimum supported value is 0. |