VERIFIED SOLUTION i

How to change the database connection information for the EngageOne server

Product Feature: Installation / Upgrade

Configuration: JBoss, WebSphere, WebLogic

For JBoss

To reconfigure the JBoss data sources: update the connection configuration settings by updating the engageone-ds.xml file located in the application deploy directory in the JBOSS server.

To update the password: see “Updating database user passwords” on page 220. An application server or cluster restart is required to put the database configuration changes in to effect. In a cluster setup, synchronize the changes to all nodes prior to the restart. All nodes must point to the same database.

For WebSphere

To reconfigure the WebSphere data sources:
  1. Using the WebSphere console, navigate to each data source (jdbc/ocm and jdbc/ocm-nonjta) by going to Resources > JDBC > Data sources and updating the data sources one at a time.
  2. In the configuration page of each data source, change the settings where applicable. You can change the database name, server name, instance name, and port number. Alternatively, if your version of WebSphere does not display the database name, server name, instance name, and port number on this configuration page, you change the settings in the custom properties of the data source by first clicking the Custom properties link of the Configuration page for each corresponding data source.
  3. For user ID and password changes, if an authentication alias is used, you will need to update the authentication alias. Otherwise, change the user ID and password via the Custom properties.
An application server or cluster restart is required to apply the database configuration
changes. In a cluster setup, synchronize the changes to all nodes prior to the restart. All nodes
must point to the same database.

For WebLogic:
See the EngageOne Installation Guide for more information.

 

For Batch:

To reconfigure the batch connection configuration:
Use Engageone Administration Configuration tab or follow the instructions below.

1. Update the configuration settings pertaining to the batch database connection:
i. Always backup config-settings.xml before any modifications.
ii. Open config-settings.xml, located in the active-drive/conf directory.
iii. Edit the value of the settings for the following keys:
com.pb.engageone.server.batchjdbc.urlEnter the connection string in the following format using your respective values:
jdbc:sqlserver//<DATABASELOCATION>:<PORT>;
databaseName=<DATABASE NAME>
com.pb.engageone.server.batchjdbc.usernameEnter the respective DATABASE USERID
NA Batch properties For more information, see “Non-accumulated batch” in the Admin guide

2. If necessary run the change password script as described in “Updating database user passwords” in the Admin guide.

You can find this documented in the "EngageOne Server Administration Guide" under Managing your EngageOne environment->Disaster recovery->Database location or name changed. For 3.x that should be on page 207
UPDATED:  November 3, 2017