To update notification and messaging bus configuration from CLI, we can use the script from <Configure_Home>\admin\<enteripse_Name>\samples on the AMX Admin machine.

CLI for editing the configuration of messaging bus:

• environment_data.xml
• environmnet_build.xml

• qin_data.xml
• qin_build.xml

Note: Before performing the steps please take a full offline backup along with the files system (TIBCO_HOME and CONFIG_HOME, EMS) and database backup.

Before performing the steps make sure both EMS servers are running (current and new ).
 

Steps to Change the Messaging Bus And Notification Bus Using CLI:

1.) Messaging Bus:

a.) For Non-SystemEnvironment:

i.) Stop all the applications under this Environment. (Alternate way to stop the Nodes in this Environment but don't stop the SystemNode)

ii.) Go to the directory: CONFIG_HOME\data\admin\amxadmin\samples.

iii.) Open and edit the following details in the environment_data.xml:

• a.) name under Environment tag. which is the environment name for which you want to change the messaging bus.
• b.) name under the host tag. which is the hostname under this environment.
• c.) Provide the EMS url in emsServerURL of new EMS Server.
• d.) add these 2 properties in the MessagingBus tag and give the appropriate value for them.
  • 1.) emsConnectionUsername="admin" 
  • 2.) emsConnectionPassword="" 

save the changes in the file.

iv.) Now from the same directory ( CONFIG_HOME\data\admin\amxadmin\samples)

run the below cmd. (make sure you have configured it on the server)

ant -f environment_build.xml setMessagingBus

v.) If you have stopped the node in step i.), then after seeing this below the log-in console starts the nodes immediately.

log for reference:

==================================

 **** Some runtime nodes (or their hosts) are NOT running. Runtime tasks will keep waiting until these nodes come up *****

[AMXAdminTask] 02 Jul 2021 14:55:50 WARN - Node 'DevNode' or its host 'SystemHost' is NOT running.

==================================

vi.) After starting the node check if there is an error on the tibcohost log and check from the admin UI if the changes have occurred.

b.) For System Environment:

i.) Stop all the applications under SystemNode. (don't stop the SystemNode).

ii.) Change the environment_data.xml for SystemEnvironment.

iii.) Run the cmd ant -f environment_build.xml setMessagingBus.

iv.) After the build is successful, start the application under the SystemNode.

2.) For Notification Bus:

i.) Go to the directory: CONFIG_HOME\data\admin\amxadmin\samples.

ii.) Open and edit the following details in the qin_data.xml:

groupName: will be your Enterprise name.

userName: username for EMS server.

password: password for EMS server

serverURL : EMS server URL.

iii.) Save the changes and run the below cmd:

ant -f qin_build.xml setNotifyConfig

wait for the build to complete.