The fields on the Server Properties page correspond to the parameters in the tibemsd.conf configuration file. The fields have been organized to mirror the parameter categorization given in the
TIBCO Enterprise Message Service User’s Guide, as shown here:
The FT Active radio button determines the ft_active parameter setting for the secondary server. The
ft_active setting for the primay server is determined by the Secondary Listens URL settings in the main
Fault Tolerance page.
The URLs entered here are used by the Central Administration server to communicate with the EMS server. If fault tolerance is configured, you must add two EMSCA Deployment Listens.
The Fault Tolerance properties page determines the behavior of EMS servers in a fault tolerant pair. The fields on this page correspond to the
Fault Tolerance Parameters parameters in the
tibemsd.conf configuration file, and influence the behavior of both the primary and secondary servers in the pair.
Fault tolerant pairs share a single JSON configuration file. To configure the secondary EMS server, add a Secondary Listens URL for each URL on which the EMS server should listen in the event that it becomes active. Click the
FT Active radio button next to the Secondary Listens URL that the primary server should use to check the secondary server heartbeat.
The Validation Results page shows a list of any validation errors in the current server configuration. Each time you edit a field, the Central Administration validates the revised server configuration and reports any errors in the Validation Results page. Immediate feedback is provided through the Validation Results link in the sidebar. The number of errors, if any are present in the server configuration, appears to the right of the link name.
A description of each validation issue is listed on the Validation Results page. Click the View

icon to navigate to the properties page where the issue is located.
The JSON Source page displays a read-only copy of the server configuration file that is currently stored in the working directory. This file contains any edits that have been made but not yet deployed to the server.