![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
On a computer running Microsoft Windows, you can start the EMS server from the Start menu, following the path: Programs > TIBCO > TIBCO EMS 7.0 > Start EMS Server On Windows systems the tibemsd.exe and tibemsmcd.exe files run as administrator to enable multicast functionality and to let the tibemsd.exe modify the configuration files.To start the EMS server from the command line using the preconfigured setup, navigate to EMS_HOME/bin and run the script:Running the script starts the EMS server using the configuration files in the default location, config-file-directory\cfmgmt\ems\data directory, where the config-file-directory corresponds to the Configuration Directory specified during installation.
Users using the Central Administration feature must start the EMS server in JSON mode. This is done from the command line, using the -config option to specify the JSON configuration file. For more information, see JSON Configuration Files in the TIBCO Enterprise Message Service Central Administration guide.Your JSON-configured tibemsd must be running before it can be added to the Central Administration server list. To start the TIBCO Enterprise Message Service server using the JSON configuration file:
1. tibemsd -config json-file-pathwhere json-file-path is the path to your JSON configuration file. For example:When started using the JSON configuration, the tibemsd silently ignores any unknown parameters. For example, no configuration errors are thrown if the tibemsd.json file contains an obsolete parameter.
For information on converting .conf configuration files to JSON configuration files, see Converting Server Configuration Files to JSON in the TIBCO Enterprise Message Service Central Administration guide.In Central Administration, fault tolerant pairs share a single JSON configuration file. Primary and secondary server roles are determined when the servers are started.Start the primary EMS server as usual. Start the secondary server using the -secondary flag. For example, where the JSON configuration file is tibemsd.json:
The preconfigured EMS server files are located in the config-file-directory\cfmgmt\ems\data directory, where the config-file-directory corresponds to the Configuration Directory specified during installation. For more information, see Installing TIBCO Enterprise Message Service in TIBCO Enterprise Message Service Installation.Change the directory to the installed data directory:./tibemsd -config "config-file-directory/cfmgmt/ems/data/tibemsd.conf”.\tibemsd -config “config-file-directory\cfmgmt\ems\data\tibemsd.conf”Alternately, change to the EMS_HOME\samples\config directory and create a datastore directory (or other directories as needed) to use the sample configuration files there.The EMS server dynamically loads the SSL and compression shared libraries, rather than statically linking them. If the tibemsd executable is executed from the data directory, it automatically locates these libraries. If the server is moved elsewhere, the shared library directory must be moved as well.Task B Start the tibemsdwhere options are described in Table 14. The command options to tibemsd are similar to the parameters you specify in tibemsd.conf, and the command options override any value specified in the parameters. See tibemsd.conf on page 177 for more information about configuration parameters.
Table 14 tibemsd Options -config config file name config file name is the name of the main configuration file for tibemsd server. Default is tibemsd.conf.For example, to start an EMS server using the default JSON configuration file, use: -trace items Specifies the trace items. These items are not stored in the configuration file. The value has the same format as the value of log_trace parameter specified with set server command of the administration tool; see Tracing on the Server. Specifies the secondary server in a fault tolerant pair. This option is only valid for EMS servers started using JSON config -ssl_password string Print the certificates loaded by the server and do more detailed tracing of SSL-related situation. -ft_active active_url URL of the active server. If this server can connect to the active server, it will act as a backup server. If this server cannot connect to the active server, it will become the active server. -ft_heartbeat seconds -ft_activation seconds Activation interval (maximum length of time between heartbeat signals) which indicates that active server has failed. Set in seconds: default is 10. This interval should be set to at least twice the heartbeat interval. Causes the sever to delete corrupted messages in the store files, allowing the server to start even if it encounters errors.Note that using this option causes data loss, and it is important to backup store files before using -forceStart. See Error Recovery Policy for more information.You can stop the EMS server by means of the shutdown command from the EMS Administration Tool.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |