When updating database parameters in BusinessConnect (such as for changing a database password, or changing the database server), the following areas should be considered, the BC configuration store, and the locations of the BC schemas associated with your BusinessConnect installation.  The resolution below will guide you as to what needs to be changed when database parameters need to be changed in your BC environment.
 

Here are the areas to consider when changing database parameters with BusinessConnect.

all platforms

You will have to undeploy and delete your existing BC deployment to your BC engines, and you will have to then generate, configure, and deploy a new BC deployment if:

1.  If you are changing the main configuration store location (under Administrator>BusinessConnect>Manage installation), or
2.  You are updating the bc-check-point-db setting under (under Administrator>BusinessConnect>System Settings>Audit, Non-Repudiation and Runtime Database Configuration)

These JDBC settings are embedded into the BC deployment, which all engines use on startup.  Because of obfuscation of the database parameters for security reasons, the parameters can not be manually updated in the deployment.  The Administrator reads the parameters set in these two location when generating the deployment, and embeds them in the deployment itself.

You do not have to generate a new deployment if you are only updating the Audit Log, the Non Repudiation Log, or the Runtime Data Store and NOT the bc-check-point-db configuration under the JDBC settings (Administrator>BusinessConnect>System Settings>Audit, Non-Repudiation and Runtime Database Configuration).  These settings (with the exception of the bc-check-point-db setting) are read from the BC configuration store by the BC engines on startup, so there is no need for a redeployment.