Further info about the file system is mentioned in this TIBCO support link: More details about the file system that is required is mentioned in the user guide TIBCO documentation for EMS. Once the system transfers the lock to another server, pending writes queued by the previous owner must fail. Unique Write Ownership: The EMS server process that has the file lock must be the only server process that can write to the file. EMS servers use this lock to determine the primary server. The storage solution must not assign the locks to two servers simultaneously. Synchronous Write Persistence: Upon return from a synchronous write call, the storage solution guarantees that all the data have been written to durable, persistent storage.Дistributed File Locking: The EMS servers must be able to request and obtain an exclusive lock on the shared storage. (Solutions that write data blocks in any other order (for example, to enhance disk efficiency) do not satisfy this requirement.) Write Order: The storage solution must write data blocks to shared storage in the same order as they occur in the data buffer. The file system shared between the two machines must support the following criteria: If one EMS server is able to have a file lock on the datastore and it is unable to access the other EMS server, it will be the active server. EMS server will try to lock the datastore on the shared file system in order to ensure it is the active server. tcp://10.10.101.22:8222 or tcp://8222 to listen on the default IP address.ДЄuthorization should be set to enabled to verify users' passwordsДЇor EMS Fault-Tolerance configuration, the two EMS machines share the configuration files and datastore. Store path where store files will be created The main configuration file nf, determines things like listen ip address and port, EMS servername, location of other configuration files and so on.ДЇor a standalone EMS server I just set the following parameters:

To configure EMS you just take a copy from sample configuration files and edit them. I was not able to find TIBCOuniversalinstaller binary for EMS 8.5.0 so I just unzipped the files into some folder let's say /var/tibco/ems/8.5 Configuration

Using TIBCO universal installer, or by just unziping the file TIB_ems_8.5.0_linux_x86_64.zip. The connection string will be in the form tcp://server1:port1,tcp://server2:port2 Once the active server is down, the ems passive server will take over and start reading the configuration files and message store and continue accepting connections from clients. One EMS server is in active state writing and reading from the message store and configuration files. This configuration was made with TIBCO EMS 8.5.0Д®MS shared state Fault-tolerance configuration is where the configuration and message store is shared between the two EMS servers. I will describe below the main configuration steps required to configure two Linux machines with EMS installed to work together in an shared-state fault-tolerance configuration. TIBCO Enterprise Message Service provides Java Message Service ( JMS) compliant communications across a wide range of platforms and application technologies.

Tibco ems windows