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

  1. Start the WebSphere Application Server administrative console.
  2. Log in as the WebSphere Application Server administrator (default: wasadmin), or as another user with administrative privileges.
  3. In the navigation pane, expand Resources, expand JDBC, and click JDBC Providers.
    The JDBC providers page opens.
  4. 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
    1. Click the JDBC provider link.
      The JDBC provider page opens.
    2. Under Additional Properties, click Data sources
    3. 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
      1. Click the data source.
      2. Under Additional Properties, click Connection Pool Properties.
      3. In the Purge policy field, select EntirePool.
      4. Click OK.
      5. Under Additional Properties, click Custom Properties.
      6. Click clientRerouteAlternateServerName. If this property is not present, click New and add the property and value.
      7. 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.
      8. Click OK.
      9. Click clientRerouteAlternatePortNumber. If this property is not present, click New and add the property and value.
      10. 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.
      11. Click enableSeamlessFailover. If this property is not present, you can click New and add the property and value.
      12. 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.

      13. Click OK.
      14. Click New.
      15. In the Name field, type maxRetriesForClientReroute
      16. In the Value field, type 2. This parameter sets the number of connection retry attempts.
      17. Click Apply.
      18. In the Name field, type retryIntervalForClientReroute This parameter sets the sleep interval between retry attempts.
      19. 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.
      20. Click OK.
      21. Click Apply.
      22. In the Messages box at the top of the page, click Save to apply the changes to the master configuration.
      23. Click the data source name in the line at the top of the page to return to the data source page.
      24. Click Test Connection to test the connection.
      25. Repeat for all the above data sources that are listed.
    4. Repeat for all the above JDBC providers that are listed in the Administrative console.
  5. 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:
    1. Click Resources > JDBC > Data sources.
    2. In the Data sources panel, click the first data source that is listed.
    3. Under Common and required data source properties, update the server name to the virtual host name.
    4. Click Apply, then click OK.
    5. Repeat each step for every data source that is listed.
    6. 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.
    7. If a message displays that asks you to complete synchronization, follow the instructions.
  6. Log out of the console.