Legacy platform

Automatic client reroute

You can choose which cluster member that you want to reroute to.

The Sterling™ Order Management System Software application uses the following Db2® JDBC URL to connect to one of the Db2 pureScale® members.

jdbc:db2://perfdb101:50000/ster_DB

After connecting, the Db2's Automatic Client Reroute (ACR) provides a list of the available cluster members to the Db2 JDBC driver. If a cluster member fails, the driver will automatically send transactions to the surviving members.

In addition to the ACR notification, the JCC driver provides the following parameters to allow you to specify a static list of alternate servers to the Db2 JDBC driver, so that the driver knows to which cluster member to attempt, if the member that the JDBC URL is pointing to is slow.
  • jccAlternateServer
  • jccAlternateServerPort
You can set these parameters for agent and integration servers with the following parameters in the JDBC property file:
  • jdbcService.db2Pool.prop_clientRerouteAlternateServerName=perfdb101, perfdb102, perfdb103, perfdb104
  • jdbcService.db2Pool.prop_clientRerouteAlternatePortNumber=
50000,50000,50000,50000
In the WebSphere® Application Server administrative console, Db2 automatic client reroute options section, use the following fields to enable client rerouting:
  • Alternate server names - Specify the alternate server name (or alternate server names) for the Db2 server. If more than one alternate server name is specified, the names must be separated by commas. For example:

    perfdb101, perfdb102, perfdb103, perfdb104

  • Alternate port numbers - Specify the alternate server port (alternate server ports) for the Db2 server. If more than one alternate server port is specified, the ports must be separated by commas. For example:

    50000,50000,50000,50000