Changing configuration of other databases to high availability

You can change the operations database, the Standardization Rules Designer database, and the exceptions database to high-availability configurations.

About this task

You can change databases that support InfoSphere® Information Server components to high-availability configurations. These instructions apply to the following databases:
  • operations database
  • Standardization Rules Designer database
  • exceptions database

For information about configuring the active metadata repository and staging area for high-availability, see Metadata repository tier clustering for high availability.

The following instructions assume that the database already exists and is configured for non-high availability operation.

Procedure

  1. Use the RepositoryAdmin tool to change the RepositoryConnection.connectionURL property of the database to a new URL.
    Use the following commands, depending on the type of database system in use. See RepositoryAdmin tool reference for more information.
    Db2 cluster or Db2 HADR
    (The following is a single command although shown in this document on multiple lines.)
    RepositoryAdmin.sh -uc -rn reposName -cn reposConnName -cr
    'jdbc:db2://host:port/databaseName;
    clientRerouteAlternateServerName=alternate_host;
    clientRerouteAlternatePortNumber=alternate_port;
    enableSeamlessFailover=1;maxRetriesForClientReroute=2;
    retryIntervalForClientReroute=15;'
    Oracle RAC
    (The following is a single command although shown in this document on multiple lines.)
    RepositoryAdmin.sh -uc -rn reposName -cn reposConnName -cr
    'jdbc:ibm:oracle://host:port;serviceName=serviceName;
    alternateServers=rac1_host:rac1_port,rac2_host:rac2_port,
    rac3_host:rac3_port'
  2. For the operations database and the exceptions database, use the RegistrationCommand tool to update the connection configuration file for the database on each engine tier computer. You must run this command on each engine tier computer that has a directory that corresponds to the relevant data store. The connection configuration file is used to connect the engine tier to the database.
    Note: This step is not required for the Standardization Rules Designer database. For the Standardization Rules Designer database, go to step 3.
    The values of connection properties in the configuration file that are also specified by tokens in the template file are replaced. The result is written to the output file that is specified with the -results parameter. The following parameters will be replaced if found in the specified template file: @DBTYPE@, @DRIVER_CLASS@, @DRIVER_JARFILES@, @CONNECTION_URL@, @DATABASE_USER@, @PASSWORD@.
    1. Change to the directory that is associated with the database.
      For example, for the operations database, if you used the default name DSODB, change to the directory install_dir/Server/DSODB. For the exceptions database, if you used the default name ESDB, change to the directory install_dir/Server/ESDB.
    2. Run the RegistrationCommand tool with the following syntax, where:
      • install_dir is the directory where you installed IBM® InfoSphere Information Server.
      • repos_dir is the directory for the database.

      (The ⇒ character indicates a line continuation):

      Operating system Command
      AIX Linux
      cd install_dir/Server/repos_dir
      
      ../../ASBNode/bin/RegistrationCommand.sh -get_config ⇒
      -authfile credentials_file -repository ⇒
      repository_name -configfile ⇒
      config_file_template -results ⇒
      output_file
      For example:
      cd /opt/IBM/InformationServer/Server/DSODB
      
      ../../ASBNode/bin/RegistrationCommand.sh -get_config ⇒
      -authfile isadminCredentials.txt -repository_name DSODB ⇒
      -configfile DSODBConnect.tmpl -results DSODBConnect.cfg
      Windows
      cd C:\install_dir\Server\repos_dir
      
      ..\..\ASBNode\bin\RegistrationCommand.bat -get_config ⇒
      -authfile credentials_file -repository ⇒
      repository_name -configfile ⇒
      config_file_template -results ⇒
      output_file
      For example:
      cd C:\IBM\InformationServer\Server\DSODB
      
      ..\..\ASBNode/bin/RegistrationCommand.bat -get_config ⇒
      -authfile isadminCredentials.txt -repository_name DSODB ⇒
      -configfile DSODBConnect.tmpl -results DSODBConnect.cfg
  3. For the Standardization Rules Designer database, reconfigure the application server data source if you are using WebSphere® Application Server Network Deployment.
    Refer to Modifying the connection properties for data sources for the InfoSphere QualityStage Standardization Rules Designer database for specific instructions.
    Important: IBM InfoSphere QualityStage Standardization Rules Designer will not be supported after 31 December 2020. No replacement is planned.