WebSphere Application Server Network Deployment: Specifying the alternate address and port for a Db2 clustered database
For IBM® WebSphere® Application Server Network Deployment to communicate with more than one server, specify an alternate address and port for a Db2 database.
Procedure
- Start the WebSphere Application Server administrative console.
- Log in as the WebSphere Application Server administrator (default: wasadmin), or as another user with administrative privileges.
- In the navigation pane, expand Resources,
expand JDBC, and click JDBC Providers.
The JDBC providers page opens.
- Complete the following steps for each of
these JDBC providers that might be listed in the Administrative console:
- ASB JDBC Provider
- ASB XA JDBC Provider
- QSSRD Repository JDBC Provider
- QSSRD Repository XA JDBC Provider
- Click the JDBC provider link.
The JDBC provider page opens.
- Under Additional Properties, click Data sources
- Complete the following steps for each of these data
sources that might be listed in the Administrative console:
- ASB JDBC DataSource
- ASB JDBC XA DataSource
- ASB JDBC Staging XA DataSource
- JReport JDBC DataSource
- QSSRD DataSource
- QSSRD Global XA DataSource
- Click the data source.
- Under Additional Properties, click Connection Pool Properties.
- In the Purge policy field, select EntirePool.
- Click OK.
- Under Additional Properties, click Custom Properties.
- Click clientRerouteAlternateServerName. If this property is not present, click New and add the property and value.
- In the Value field, type the alternate
server address:
- If IBM Tivoli® System Automation for Multiplatforms (SA MP) is running in the cluster, type the service IP address that the cluster nodes share.
- If SA MP is this not running in the cluster, type the IP address of the standby server.
- Click OK.
- Click clientRerouteAlternatePortNumber. If this property is not present, click New and add the property and value.
- In the Value field, type the alternate
server port number:
- If SA MP is running in the cluster, type the service port number that the cluster nodes share.
- If SA MP is not running in the cluster, type the port number of the standby server.
- Click enableSeamlessFailover. If this property is not present, you can click New and add the property and value.
- In the Value field, type
1
.This property controls whether the server returns an error that indicates that failover occurred. For more information, see the Db2® database system documentation.
- Click OK.
- Click New.
- In the Name field, type
maxRetriesForClientReroute
- In the Value field, type
2
. This parameter sets the number of connection retry attempts. - Click Apply.
- In the Name field, type
retryIntervalForClientReroute
This parameter sets the sleep interval between retry attempts. - In the Value file, type
15
.Note: You might want to set these values differently. The values you choose depend upon the hardware and the topology of your configuration. - Click OK.
- Click Apply.
- In the Messages box at the top of the page, click Save to apply the changes to the master configuration.
- Click the data source name in the line at the top of the page to return to the data source page.
- Click Test Connection to test the connection.
- Repeat for all the above data sources that are listed.
- Repeat for all the above JDBC providers that are listed in the Administrative console.
- If your metadata repository is configured for
active-passive failover, but you did not indicate the virtual host
name for your metadata repository database in the IBM
InfoSphere® Information Server installation
program, complete the following steps:
- Click Resources > JDBC > Data sources.
- In the Data sources panel, click the first data source that is listed.
- Under Common and required data source properties, update the server name to the virtual host name.
- Click Apply, then click OK.
- Repeat each step for every data source that is listed.
- Click Test connection. Ensure that you see a message that says, The test connection operation for data source data_source_name on server server_name at node node_name was successful.
- If a message displays that asks you to complete synchronization, follow the instructions.
- Log out of the console.