Update the database user registry

After creating and use the database user registry, we can update the database user ID, password, and where the data is stored. This task does not change the DN structure stored in the database repository.

In a stand-alone server environment, complete the following task when the servers are either stopped or started. In a clustered environment, start the deployment manager and node agent. Then, verify they are able to synchronize.

If we plan to change the database where data is stored, populate the new database with all necessary VMM tables and create the data sources in WebSphere Application Server. Then, run this task. Read the following information for information about setting up a VMM database. After you populate the new database, restart the WebSphere_Portal server.

Set up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin commands

If we change the database administrator password, complete the steps in Change database passwords used by WebSphere Portal before running this task.

Use the wp_add_DB.properties helper file in the WP_PROFILE/ConfigEngine/config/helpers directory to ensure the correct properties are entered. In the following instructions, where the step refers to wkplc.properties, use the wp_add_DB.properties helper file.

1. cd WP_PROFILE/ConfigEngine/properties

2. Edit wkplc.properties

3. Enter the following parameters in wkplc.properties under Federated DB repository heading:
   • federated.db.DataSourceName
   • federated.db.DbType
   • federated.db.DbUrl
   • federated.db.id
   • federated.db.DbUser
   • federated.db.DbPassword

4. Save the changes to wkplc.properties.

5. Delete the required repository:
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh wp-update-db -DWasPassword=foo

6. Stop and restart the appropriate servers to propagate the changes.

Parent Update the user registry

Related tasks:

Start and stop servers, deployment managers, and node agents