Server migration planned in which the servername/hostname and IP address will be changed. What needs to be changed in EMS?
book
Article ID: KB0085216
calendar_today
Updated On:
Products
Versions
TIBCO Enterprise Message Service
-
Not Applicable
-
Description
Resolution:
1). Change the listen parameter in the tibemsd.conf file reflecting the new IP address. 2). Change the factories.conf file to reflect the new IP address of the machine if you do JNDI lookups in your applications. 3). If using RV-EMS bridge, you need to change the transports.conf and tibrvcm.conf files to reflect the new IP address of the RVD box. 4). If using routes in EMS, you have to change the IP address of all respective route EMS server boxes that are affected by the change in the routes.conf files. 5). Change the EMS server connection URL for all client applications connecting to the EMS servers whose IP addresses are changed.
Modify the tibemsd.conf, routes.conf, factories.conf, transports.conf and tibrv.conf files accordingly to reflect the new IP address/hostname. For all other EMS servers connecting to the new servers via route or fault tolerance, change the IP address/hostname in the main config file (tibemsd.conf) and routes.conf of all other EMS servers connecting to the newly IP named EMS server. Make sure that all EMS clients point to the new IP address/hostname if any are used in the connection URL.
We recommend trying the above steps in a test environment before implementing in production.
Issue/Introduction
Server migration planned in which the servername/hostname and IP address will be changed. What needs to be changed in EMS?