Resolution:
Description:
=========
Exporting destination and bridge configuration from one EMS Server to another.

Environment:
=========
All

Resolution:
=========


You can copy all configuration files except the main configuration file. Just copying queues.conf, topics.conf and bridges.conf may not be adequate in all situations as the destinations and bridges defined in those files may have the following dependencies on the following configuration files:

acl.conf – Contains information regarding access control for various destinations which need configuration information from the files users.conf and groups.conf

transport.conf – This file defines transports for importing messages from or exporting messages to external message services, such as TIBCO Rendezvous and TIBCO SmartSockets. If your destination is using the import property which allows messages published by an external system to be received by an EMS destination (a topic or a queue), as long as the transport to the external system is configured then this file also needs to be copied.

tibrvcm.conf – This file defines the TIBCO Rendezvous certified messaging (RVCM) listeners for use by topics that export messages to a tibrvcm transport.

durable.conf – This file defines static durable subscribers.

routes.conf – This file defines routes between this TIBCO Enterprise Message Service server and other TIBCO Enterprise Message Service servers. So if your queue or topic is routed then this file is also needed.

It is suggested that you copy all configuration files from server A to server B except the tibemsd.conf file if you want to export queues and bridges. Additionally, if you want to have a replica of server A on server B then you can copy the whole set of configuration files to server B. It is important to remember to change the various paths to match those of the other configuration files, log files and datastore file locations according to your Server B.

Keywords/Tags:
==========
export queues,export topics,export bridges,server replica

Exporting destination and bridge configuration from one EMS Server to another.