# Conversion of Server Configuration Files to JSON

The `tibemsconf2json` utility is provided to convert a set of text-based EMS server configuration files into a single JSON configuration file. This tool is available on platforms that support Central Administration.

For a list of supported platforms, see the supported platforms list for "Central Administration" in the TIBCO Enterprise Message Service Installation guide.

When using the utility, keep in mind that:

- If there are any unsupported parameters in the source configuration file, the `tibemsconf2json` utility issues a warning but continues converting.

  Review the TIBCO Enterprise Message Service Release Notes for details about any obsolete parameters that were removed from the current release.

- To convert a fault tolerant pair, use the -secondaryconf option to merge the two `tibemsd.conf` files of a fault tolerant pair of servers.

## Syntax

To convert a EMS server configuration to JSON, use the command:

    tibemsconf2json -conf source-file [-secondaryconf ft-source-file]  [-confencoding character-set-name] -json output-file | -console

where

- source-file is the path to the `tibemsd.conf` to be converted. Sub-file names and locations are derived from the content of the `tibemsd.conf` file. When converting servers in a fault tolerant pair, specify the configuration file for the primary server.
- ft-source-file is the path to the server configuration file for the second server in a fault tolerant pair. Specify this path with the `-secondaryconf` option to convert a fault tolerant pair.
- character-set-name is the name of the character set that was used to encode the source-file (and ft-source-file, if given). Any character encoding supported by the Java SE platform can be specified. Specify the encoding using the Canonical Name for java.lang API.

  When omitted, the expected encoding is UTF-8. Note that the output JSON file is always encoded with UTF-8.

- output-file is the name and location of the new JSON file. This file must have the `.json` extension. For example, `tibemsd.json`. If no path is specified, the file is created in the current working directory.
- Alternately, specify `-console` to display the JSON output to the screen rather than saving to file.

The `tibemsconf2json` utility converts the `.conf` file to a JSON-based configuration.

If `-json` output-file is specified, the file is created and saved in the location specified, or the current working directory if no path is given. You can then start the EMS server using the JSON configuration, and access the server through the Central Administration web interface.

## Convert a Fault Tolerant Pair

If a `-secondaryconf` ft-source-file is specified, the `tibemsconf2json` utility first converts the primary configuration to JSON, then uses the secondary configuration to complete the fault tolerant setup, deciding which one of the primary listen URLs must be marked as FT Active and adding extra secondary listen URLs, if any.

Note that the secondary configuration is used only for the purpose of completing the fault tolerant setup. With the only exception of the `logfile` property, any differences and discrepancies between the two initial sets of configuration files that are outside fault tolerance parameters are ignored.

Copyright © Cloud Software Group, Inc. All rights reserved.