Messaging Server
Use the fault tolerant mechanism provided by the TIBCO Enterprise Message Service servers to configure two servers - one being the primary server and the other as standby server. The primary server accepts client connections or requests and interacts with clients to send or receive messages. If the primary server fails, the standby server takes over; it becomes the new active server and resumes the operation. It does not support more than two servers in this configuration. TIBCO Enterprise Message Service provides you options to configure shared state and unshared state failover. To avoid message loss, duplication or out of order message delivery, it is always preferred to use shared state failover.
Implementing on a Shared Disk File System
To prevent disk failures and outages, include the TIBCO Enterprise Message Service server logs, configuration files and file stores on a shared Storage Area Network to be accessed by multiple nodes. The shared disk subsystem must be accessible from standby servers to prevent disk failures or node outages from causing a prolonged JMS Server outage. This helps you to restart the Messaging server from another node.