Creating Service Name Aliases for TIBCO ActiveMatrix BPM Databases

On both the primary site and the DR site, create a service name alias that TIBCO ActiveMatrix BPM can use to identify the database to which it connects.

TIBCO ActiveMatrix BPM uses a JDBC connect string to identify the Oracle database to which it connects. The connect string identifies the database by its service name which, by default, is the same as its SID.

Because the databases on the primary and DR site have different SIDs, you must define an Oracle service name that TIBCO ActiveMatrix BPM can use as an alias, allowing it to connect to the database whether it is currently running on the primary system or the DR system.

Note: The use of an alias means that the physical location of the DBMS makes no difference to the recovery scenario.

Procedure

  1. On the primary system database, define a service name alias. For example, to define a service name alias of amxbpmdb on the primary system database (which has a SID of main):
    1. Verify that the SERVICE_NAMES parameter only contains a single name, which is the SID:
      SHOW PARAMETER SERVICE_NAMES ;
    2. Modify the SERVICE_NAMES parameter to add the amxbpmdb alias:
      ALTER SYSTEM SET SERVICE_NAMES = 'main,amxbpmdb' ;
  2. On the DR system database, define the same service name alias. For example, to define a service name alias of amxbpmdb on the DR system database (which has a SID of second), run the following commands:

    SHOW PARAMETER SERVICE_NAMES ;

    ALTER SYSTEM SET SERVICE_NAMES = 'second,amxbpmdb' ;

Result

When you configure the EMS server and TIBCO ActiveMatrix BPM, you can specify the JDBC connect string as:

jdbc:oracle:thin:@db-host-name:db-port-num/alias-service-name

instead of the default:

jdbc:oracle:thin:@db-host-name:db-port-num:service-name

For example:

jdbc:oracle:thin:@db-host-name:db-port-num/amxbpmdb

Note: The service-name is preceded by a forward-slash character (’/’) not a colon (’:’).