Before Starting TIBCO ActiveMatrix BPM on the Secondary Site

Procedure

  1. Promote your Oracle Data Guard DBMS on the secondary site to online status, and start all required support software (such as EMS) on the secondary site.
  2. Roll back and purge any outstanding global transactions in the Oracle database associated with TIBCO ActiveMatrix BPM:
    1. Using a text editor, open the following script:
      TIBCO_HOME\bpm\n.n\samples\DRscripts\clean-ora-tran.sh
    2. In the following line, replace the example value bpmuser with the name of the operating system account that runs TIBCO ActiveMatrix BPM.
      SQL_OS_USER=bpmuser
    3. Save the file.
    4. Using the Oracle system DBA account, run the clean-ora-tran.sh script.

      This script identifies any outstanding global transaction records associated with TIBCO ActiveMatrix BPM, and generates a bpm-tx-rollback.sql script that contains a set of SQL commands to purge them.

    5. Review the generated bpm-tx-rollback.sql script to ensure that you are happy with the changes it will make to the database. For example, depending on what applications use the BPM database in your particular environment, there might be non-BPM transactions in the database: if so, do these need to be rolled back or not?
    6. Using the Oracle SQLPlus utility, run the bpm-tx-rollback.sql script to purge the outstanding global transactions.
  3. Purge all pending transactions in EMS. To do this:
    1. As the EMS admin user, run the following script:
      TIBCO_HOME\bpm\n.n\samples\DRscripts\clean-ems-tran.sh

      (Make sure that the EMS server’s bin directory is in the PATH.) This script identifies any pended transactions, and generates anemsrollback.sh file that contains a set of tibemsadmin commands to purge them.

    2. Review the generated emsrollback.sh script to ensure that you are happy with the changes it will make to the EMS datastore.
    3. Use the following command to run the script and purge all pending transactions:
      tibemsadmin -script emsrollback.sh

      See the TIBCO Enterprise Message Service User’s Guide for more information.

  4. Remove any TIBCO ActiveMatrix BPM nodename TxM log files from the following locations (if they exist):
    CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/work/HowlLogs

    CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/work/GeronimoTMID

    where nodeName is the name of each node on the system - for example, BPMNode and SystemNode. See Transaction Manager Log Files for more information.

  5. Remove the following lock file (it may or may not exist, depending on the file replication system being used):
    CONFIG_HOME/tibcohost/Admin-enterpriseName-adminServerName/nodes/nodeName/bin/node.lck

    where nodeName is the name of each node on the system - for example, BPMNode and SystemNode.