A Distributed ActiveMatrix BPM System

In a production environment, TIBCO recommend the use of a distributed configuration for ActiveMatrix BPM (along with a suitable underlying architecture).

This configuration can provide the following advantages:

  • Scalability: ActiveMatrix BPM software provides specialization and horizontal scalability capabilities. You can:
    • add BPM logical nodes to boost the capacity of the BPM system in the required areas - web tier, process management or work management.
    • distribute BPM logical nodes to different TIBCO Host instances and physical machines as required.

      See "TIBCO ActiveMatrix BPM Logical Nodes and Services" in BPM Concepts for more information about the different types of BPM logical node and their uses.

  • High availability and fault tolerance: ActiveMatrix BPM software provides active/active clustering capabilities. Adding a second BPM logical node (of type BPM) provides high availability and fault tolerance. In the event of a system-affecting failure on one node, load is automatically switched to the remaining node.
Note: TIBCO also recommend that the ActiveMatrix Administrator server is hosted independently from ActiveMatrix BPM, using its own set of TIBCO Host instances.

You must create the ActiveMatrix Administrator server (if it does not already exist) before you create the distributed BPM system. See Creating an ActiveMatrix Administrator Server (Single or Replicated) for more information about how to do this.

The following figure shows an example configuration for a distributed ActiveMatrix BPM system.

Example configuration for a distributed ActiveMatrix BPM system
Note: For details of the associated ActiveMatrix Administrator server configuration, see Example configuration for a single ActiveMatrix Administrator server or Example configuration for a replicated ActiveMatrix Administrator server.