Change datasource password in a clustered env.

If you're federated, config manager detects this and attempts to connect to the DMGR pocess via it's SOAP port.It then instructs the DMGR to update the EJB module's configuration (the datasource password). This information will be stored on the DMGR in the config/cells//applications//deployments///META-INF/ibm-ejb-bnd.xmi file.If automatic sync is enabled, the change will be synced to all of the nodes running that app automatically after a period of time. (This is the default) The sync requires that the node agent is running.If automatic sync is disabled, you'll need to manually sync each node that runs the app.

Based on my quick analysis of the code yes, we will use the WAS APIs to modify the datasource password a per module basis. The password will be stored in the ibm-ejb-bnd.xmi file for each EJB module in directories as you have mentioned below.Does WAS need to be running? If you are federated to a DMGR, yes we will connect to the DMGR process and ask it to do the configuration changes. If not federated, we will not connect to any process. The WAS APIs we use will update the files directly on the file system without connecting to any WAS server.A bit of background:The datasource itself can have a default password.This password can be overridden at the MODULE levelThis password can also be overridden at the BEAN level.Config manager sets the password at the MODULE level in 5.6.x (WAS5AdminClient.mapEjbsToDataSource(). (6.0 is different)