Using Third-Party Solutions to Configure a High Availability, Fault Tolerant ActiveMatrix BPM System

In the event of a hardware failure resulting in the failure of TIBCO ActiveMatrix BPM, a highly available, fault tolerant system can start TIBCO ActiveMatrix BPM on another machine, thus ensuring limited service interruption and no loss of data or messages.

The following figure illustrates the use of third-party solutions to provide highly available, fault tolerant capabilities to your BPM runtime.

High availability ActiveMatrix BPM system using third-party solutions

The setup requires at least three machines, say M1, M2, and M3, where:

  • TIBCO ActiveMatrix BPM (or at least the data folder) is on the shared file system which is only available to the machine that has a fully operational TIBCO ActiveMatrix BPM node installed and running.
  • TIBCO ActiveMatrix BPM and TIBCO ActiveMatrix Administrator are installed and running on one machine (M1).
  • The other machines (M2 and M3) are:
    • connected to a shared file system
    • part of an active-passive clustering setup. At any given time, one of the machines will have access to the shared file system on which the TIBCO ActiveMatrix BPM Node is installed/running.

      In case of any catastrophic event such as power loss, hardware failure, network disruption, or operating system crash, the cluster software detects it and fails over to the next available server.

    • One of these two machines should have a fully operational TIBCO ActiveMatrix BPM node installed and running.