Installation guide
TIBCO ActiveMatrix BPM Installation and Configuration
20
|
Chapter 2 Pre-install Considerations
Determine the Architecture for Your System
The architecture of a system depends on various factors such as:
• Number of users for the system (includes registered, concurrent, and active
users).
• Scalability
• Performance expectations
• Typical work volumes such as the number of work items, pageflows, business
services, or enterprise processes that need to be processed per minute.
Depending on your requirements, you can choose one of the following:
High availability, fault-tolerant (HA-FT) System
In the event of a hardware failure resulting in the failure of TIBCO ActiveMatrix
BPM, a highly available, fault tolerant system starts TIBCO ActiveMatrix BPM on
another machine, thus ensuring limited service interruption and no loss of data or
messages. Setting up this architecture also involves distributing the components
over different machines. See Highly Available and Fault Tolerant System for
details.
Setting up a Highly Available, Fault Tolerant System describes how to set up a
highly available, fault tolerant system using a third-party solution or active-active
clustering.
Distributed System (without HA-FT features)
Logical nodes can also be distributed to different physical noes, to provide
specialization and horizontal scalability capabilities according to the enterprise’s
needs. A distributed system enables you to scale only certain components of the
BPM runtime so as to boost the performance of your system. See Distributed
System for details.
For example, if your services exercise the Process Manager component the most,
you can configure the Process Manager component on a different host. You can
then scale it up by adding more Process Manager components (or scale it down by
removing some Process Manager components) on that host without affecting the
rest of the system.
Setting up a Distributed System describes how to set up a distributed system.