Resolution:
Yes. When EMS fails over, all the config files are getting loaded again by the secondary
server when primary goes down and secondary takes over as the primary server.
In that case, the two config files on primary and secondary should be identical to
each other so that, secondary  server will be as same that of the previous primary
server. In order to achieve this, you have two options:

1)    Share all the config files except tibemsd.conf file by placing them on the shared
storage across the FT server. You can use the same storage device which is used for DB files.

2)    Manually sync the files on other server when it gets changed on another server to
make sure that both have the identical copies.

In the above two options, the first option of sharing the config file across the FT
server is easier compared with manually syncing the files. There is a possibility that
we might forget to update the files after introducing some changes in the config
files.

For example, if we create a queue on a server which is primary now and queues.conf
file is not shared, we should update that change on the secondary's queues.conf. If we
forgot to change means, secondary server won't be having that queue when it becomes
active. Suppose if we added manually, those queue will be there as config files are getting
loaded during the failover time. But we have to do this manually every time when
config files get changed on a server.

So we would recommend the customer to share the config files using shared storage.

Can we share the config files across the EMS FT servers?