Configuring Oracle Real Application Cluster (RAC) for use with IBM Business Process Manager

Oracle Real Application Clusters (RAC) is an option of an Oracle database that brings together two or more computers to form a clustered database that behaves as a single system. In a RAC database, Oracle processes that run in separate nodes access the same data from a shared disk storage.

About this task

There are two scenarios to consider:
IBM Business Process Manager always creates the JDBC URL in the following format
jdbc:oracle:thin:@//[LISTENER_HOST][:LISTENER_PORT]/SERVICE
which can be edited to the following format to use Oracle RAC:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST= 
                  (ADDRESS=(PROTOCOL=TCP)(HOST=rac-node1)(port=1521))
                  (ADDRESS=(PROTOCOL=TCP)(HOST=rac-node2)(port=1521)))
                  (FAILOVER=on)(LOAD_BALANCE=on)
                  (CONNECT_DATA=(SERVER=DEDICATED)
                  (SERVICE_NAME=<service_name>)))

If a Oracle RAC node failover occurs, IBM Business Process Manager stops processing and you might need to restart all of the IBM Business Process Manager nodes. If you experience process-recovery issues, refer to Process recovery issues in certain situations in IBM Business Process Manager V7.5.

Procedure

  1. Specify the RAC URL as the Oracle URL when you define the relevant Oracle JDBC data sources.
    1. In the administrative console, select Resources > JDBC > Data sources.
    2. Edit all the data sources using Oracle with the JDBC URL to use one of the preceding formats.
    Refer to Configuring a data source using the administrative console.
  2. Update the Authentication Alias Configuration page and run the administrative task to update the URL to use the Oracle RAC. For more information, see Modifying authentication aliases.
  3. In a network deployment environment, you must synchronize the nodes that contain Process Center, Process Server, or Performance Data Warehouse cluster members.
    1. In the administrative console, click System administration > Nodes.
    2. Select all of the nodes and click Full Resynchronize.
    3. Stop and restart all of the clusters and servers.
Parent topic: Modifying and extending an existing installation

Mapping IBM Business Process Manager configuration parameters to Oracle setup parameters

About this task

To understand how to specify the correct information during the Oracle RAC database configuration, review the following parameter mapping information to ensure that the JDBC URL is created correctly.
The format of the JDBC URL that is generated during configuration is
jdbc:oracle:thin:@//[LISTENER_HOST][:LISTENER_PORT]/SERVICE
where
  • LISTENER_HOST represents the RAC SCAN name that is defined during the Oracle RAC setup. If you do not use Oracle RAC, LISTENER_HOST is specified in the IBM BPM profile configuration parameter Database server host name.
  • LISTENER_PORT represents the RAC SCAN listener port that is defined during the Oracle RAC setup. If you do not use Oracle RAC, LISTENER_PORT is specified in the IBM BPM profile configuration parameter Server port.
  • SERVICE represents the RAC service that is configured during the Oracle RAC setup. If you do not use Oracle RAC, SERVICE is specified in the IBM BPM profile configuration parameter Common database name, for example, SID.
For example, an Oracle RAC setup with a RAC scan name of rac1.mycompany.com, a SCAN port of 1521, and a cluster-managed database service of MYSERVICE is specified with the following JDBC URL: jdbc:oracle:thin:@//rac1.mycompany.com:1521/MYSERVICE.mycompany.com