Fault Tolerance or Load Balancing Considerations

TIBCO Enterprise Message Service

Dual server deployment with shared database state and active-passive configuration. Managed by Enterprise Message Service, heartbeats are exchanged between the server instances to determine on failover when to alternate the server. Requirement for shared state, either Storage Area Network or database. Generally Storage Area Network is recommended for performance reasons, but this incurs additional hardware and software requirements as outlined in Enterprise Message Service documentation.

The alternative is to use OS-level clustering active-passive pair with the clustering software guaranteeing only one Enterprise Message Service instance accesses the shared state at any one time.

Dual server deployment by using active-active configuration, managed by Enterprise Message Service. The requirement for shared state by using Storage Area Network or database, with Storage Area Network preferred.

Generally most customer implementations do not require a load balancing configuration.

TIBCO Order Management - Long Running System

Dual server deployment. Third-party load balancer used to send UI client requests to the active server.

Run in active-active configuration and messages load the balance from Java Message Service queues. Do not use SOAP over HTTP interfaces to remove the requirement for a load balancer.

TIBCO Master Data Management

TIBCO Product and Service 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 a 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 by using JBoss cluster and active-active pair.