TIBCO ActiveMatrix Nodes

Nodes provide a discrete runtime environment for applications or application fragments. Nodes exist within an environment, and are managed by hosts. When a node is managed by a host, the node runs in its own operating system process and JVM. A host can manage multiple nodes, and these can be from multiple environments. You can also distribute an application, such as TIBCO ActiveMatrix BPM, to multiple nodes.

An enterprise using TIBCO ActiveMatrix BPM will have one or more BPM nodes, and at least one SystemNode that runs TIBCO ActiveMatrix Administrator. (The SystemNode is replicated if you use a high-availability configuration. See High Availability and Fault Tolerance - Clustered Operation.)

There is no fixed limit to the number of BPM nodes you can have. In practice, performance limitations on your particular system are likely to dictate the practical maximum number of nodes:

  • Available memory limits the number of nodes you can practicably use on a single machine.
  • If you distribute multiple BPM nodes over different machines, then since TIBCO ActiveMatrix BPM makes heavy use of the database, the capabilities of your database will be the main limiting factor.
  • Nodes used to distribute stateless applications (such as mediation components) will be less affected by database constraints.

The reasons to use multiple nodes include:

Node names must be unique, within the enterprise, within an environment and within a host.