Use the following steps to update your already configured EMS user with the newly created one in TIBCO ActiveMatrix BPM Environment :
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1.) Stop all BPM and AMX nodes including EMS instances.

2.) Take a reliable, full, offline backup of your environment. This includes below :
=====================================================
+ Filesystem - TIBCO_HOME  - from all servers including ActiveMatrix (AMX) Administrator / EMS. Preserve timestamps, please.
+ Filesystem - CONFIG_HOME - from all servers including AMX Administrator / EMS. Preserve timestamps, please.
+ Filesystem - SHARED_MOUNT used by AMX / BPM / EMS (as applicable). Preserve timestamps, please.
+ Database - AMX (required) / BPM (required) / EMS (as applicable)
==================================================
3.) Bring up EMS and AMX/BPM Hosts/Environment.

4.) Perform the below changes via TIBCO ActiveMatrix (AMX) Administrator UI :
=============================================================
I.) In the Messaging Bus: -
**************************
a.) Update messaging bus details in Non-System Environment (e.g. BPM Environment) :
------------------------
i.) Stop all the applications running under this environment including the "tibco.amx.platform" and "amx.bpm.app" applications. The best way to do this is by stopping the Nodes of Non-System Environment.
(NOTE: We only need to stop the nodes of the "Non-System Environment" DON'T stop the SystemNode. Please keep all applications running on the System Environment. Also, make sure that 'amx.artifacts.app' is running on the System Environment).
ii.) After stopping all the applications under this environment GoTo Infrastructure ---> Environment ----> Select Non-System Environment ----> Under Configuration Tab ----> messaging bus ---> update your EMS Username and password to the newly created username and password.
iii.) Test the connection. After a successful test click on 'save' followed by 'Yes' on the confirm screen.
iv.) Start all the applications or start the Node( if it was stopped in step 1) and check if everything is running fine or not.
------------------------
b.) Update messaging bus details in the System Environment :
------------------------
i.) Stop all running applications including "tibco.amx.platform" and "com.tibco.amx.platform.artifactserver" applications. Please note that the admin console will still be accessible even after stopping all applications under the System Environment.
ii.) Make sure all nodes associated with System Environment are running.
iii.) After stopping all the applications under this environment GoTo Infrastructure ---> Environment ----> Select System Environment ----> Under Configuration Tab ----> messaging bus ---> update your EMS Username and password to the newly created username and password.
iv.) Test the connection. After a successful test click on 'save' followed by 'Yes' on the confirm screen.
v.) Start all the applications or start the Node and check if everything is running fine or not.
------------------------
**************************

II.) In Notification Server: -
**************************
i.) Make sure that all hosts/nodes are running before proceeding with changing notification server details.
ii.) Goto Admin Configuration ---> Admin Server----> Transport Configuration Tab and update your EMS Username and password to the newly created username and password.
iii.) Test the connection. After a successful test click on the save button.
iv.) Goto Host and check the Action history it should be "Update notify transport configuration Successfully".
**************************

III.) For amx.bpm.app and Custom applications (If applicable): -
**************************
a) JNDI Connection Configuration :
------------------------
i.) Goto Shared Object ---> From the type drop list, select JDNI Connection Configuration to filter RT and make the scope as global and environment and application drop as *.
ii.) Change the EMS Username and password to the newly created username and password in Each RT display in the table one by one.
Select the RT --> General tab --> Make the changes in the username and password fields.
iii.) After changes have been completed, click on the save button and then one pop-up will come up, click cancel.
iv.) Goto the resource instance tab and install the resource instance.
------------------------

b) JMS Connection Factory :
------------------------
i.) Goto Shared Object ---> From the type drop list, select JMS Connection Factory to filter RT and make the scope as global and environment and application drop as *.
ii.) Change the EMS Username and password to the newly created username and password in Each RT display in the table one by one.
Select the RT --> General tab --> Make the changes in the username and password fields.
iii.) After changes have been completed, click on the save button and then one pop-up will come up, click cancel.
iv.) Goto resource instance tab install the resource instance.
------------------------

C) JMS Connection Factory Configuration :
------------------------
i.) Goto Shared Object ---> For the type drop list, select JMS Connection Factory Configuration to filter RT and make the scope global and environment and application drop as *.
ii.) Change the EMS Username and password to the newly created username and password in Each RT display in the table one by one.
Select the RT --> General tab --> Make the changes in the username and password fields.
iii.) After changes have been completed, click on the save button and then one pop-up will come up, click cancel.
iv.) Goto resource instance tab install the resource instance.
------------------------
**************************
=============================================================

5.) After performing the above steps, please restart the complete environment with clearCache option
<CONFIG_HOME>/tibcohost/<hostName>/host/bin/tibcohost stop
./tibcohost start -clearCache &

6) Perform some basic lifecycle tests and business sanity tests to make sure it works fine.
 

PLEASE NOTE :
============================================
Perform these steps in a lower environment before proceeding to Production.