Fault Tolerance or Load Balancing Considerations
Fault tolerance and load balancing recommendations vary depending on the TIBCO application you are using.
The following recommendations apply for fault tolerance and load balancing. Also, refer to the best practices for EMS.
|
Application |
Fault Tolerance |
Load Balancing |
|---|---|---|
|
TIBCO EMS |
Dual server deployment with shared database state and active-passive configuration. Managed by EMS, heartbeats are exchanged between server instances to determine on failover when to alternate the server. Requirement for shared state, either SAN or database. Generally SAN is recommended for performance reasons, but this incurs additional hardware and software requirements as outlined in EMS documentation. Alternative is to use OS-level clustering active-passive pair with the clustering software guaranteeing only one EMS instance will access the shared state at any one time. |
Dual server deployment using active-active configuration, managed by EMS. Requirement for shared state using SAN or database, with SAN preferred. Generally most customer implementations will not require a load balancing configuration. |
|
TIBCO Fulfillment Order Management System |
Dual server deployment. Third-party load balancer used to send UI client requests to the active server. |
Run in active-active configuration and allow messages to load balance from JMS queues. Do not use SOAP over HTTP interfaces to remove the requirement for a load balancer. |
|
TIBCO Master Data Management TIBCO Fulfillment Catalog |
Dual server deployment, JBoss cluster managing active-passive pair. Third-party load balancer used to send client requests to the active server. Shared storage required to maintain state between servers. |
This is a design-time component, not a high-load application and it does not require load balancing. However, load balancing could be implemented using JBoss cluster and active-active pair. |