Resolution:
Description:
==============
Configuring the log file for an EMS secondary server when starting with the "-secondary" flag using JSON configuration file.

Resolution:
===============
Central Administration 7.0 uses the same JSON configuration file to manage both servers in a fault tolerant pair. Primary and secondary server roles are determined when the servers are started.

Since EMS server Fault tolerant pairs need to share a single JSON configuration file, both primary and secondary server use the same "logfile" definition for their log file. To let the secondary server generate a logfile with the same name defined for primary server, you can define log_file need as a relative path and start secondary server in a different directory as the primary server. If you make sure the secondary server won't access the same log file as the primary server from the location where it is started, the secondary server will generate its log file.

Example:

The JSON configuration file is located under a shared directory between two machines: &ltpath to>/tibemsd.json.  You can create two directories for primary and secondary server: &ltpath to>/Primary_dir, &ltpath to>/Seconary_dir. Modify the logfile as a relative path: ./logs/server.log, you can directly modify the JSON conf file or through the EMSCA GUI. You can also modify it within the original EMS conf file and convert it to a JSON conf file.

Start primary server under &ltpath>/Primary_dir
&ltpath to>\tibemsd -config &ltpath to>/tibemsd.json

Start secondary server under &ltpath>/Secondary_dir
&ltpath to>\tibemsd -config &ltpath to>/tibemsd.json -secondary

The primary server will generate following log file : &ltpath to>/Primary_dir/logs/server.log.
The secondary server will generate following log file:  &ltpath to>/Secondary_dir/logs/server.log

Configuring the log file for an EMS secondary server when starting with the "-secondary" flag using JSON configuration file.