Types of Configuration Files
You can choose to have the TIBCO Enterprise Message Service server store configuration settings in a single JSON-based configuration file. This file holds the entire configuration of the server without the need for sub-files. Furthermore, a single JSON configuration file holds the configuration settings for a pair of fault-tolerant servers. JSON-based configuration files use the .json file extension.
The JSON configuration standard was introduced in an earlier version of EMS. Prior to that release, the configuration of the server could only be stored in a set of text-based configuration files with names ending in .conf. The main configuration file name defaults to tibemsd.conf and a set of sub-files such as queues.conf hold information on specific types of configuration items. These configuration files are described in the present book.
A server can be started either with a set of .conf files or with a single .json file. However, servers using stores of type as or FTL can only be configured with a JSON-based configuration. In this particular case, the configuration is hosted in either TIBCO ActiveSpaces or TIBCO FTL.
You can convert a text-based server configuration to a single tibemsd.json file using the tibemsconf2json utility, which is described in the Conversion of Server Configuration Files to JSON section.