Copyright © TIBCO Software Inc. All Rights Reserved

> Starting and Stopping the EMS Server
> This section describes how to start and stop the EMS server.
> Starting the EMS Server

> | On a computer running Microsoft Windows, you can start the EMS server from the Start menu, following the path: Programs > TIBCO > TIBCO EMS 6.0 > Start EMS Server
> | On UNIX systems that will run TIBCO Enterprise Message Service with multicast, the EMS server must have root privileges. This can be done either by running the EMS server from a root user account, or the EMS server can be setuid (set user ID) root, allowing any user to run tibemsd with the required root privileges. Root privileges are required because multicast uses raw sockets. Similarly, 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.

> Start Using the Default Configuration
> To start the EMS server from the command line using the preconfigured setup, navigate to EMS_HOME/bin and run the script:
> On UNIX
> tibemsd.sh
> On Windows
> tibemsd.bat
> 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.
> Start Using Options
> To start the EMS server from the command line using options:
> Task A Navigate to the data subdirectory.
> 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:
> On UNIX
> ./tibemsd -config "config-file-directory/cfmgmt/ems/data/tibemsd.conf”
> On Windows
> .\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 tibemsd
> Type tibemsd [options]
> where 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 173 for more information about configuration parameters.

> Table 14 tibemsd Options
> Option | Description
> -config config file name | config file name is the name of the main configuration file for tibemsd server. Default is tibemsd.conf.
> -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.
> -ssl_password string | Private key password.
> -ssl_trace | Print the certificates loaded by the server and do more detailed tracing of SSL-related situation.
> -ssl_debug_trace | Turns on tracing of SSL connections.
> -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 | Heartbeat signal for the active server, in seconds. Default is 3.
> -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.
> -forceStart | 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.

> Stopping the EMS Server
> You can stop the EMS server by means of the shutdown command from the EMS Administration Tool.

Copyright © TIBCO Software Inc. All Rights Reserved