Update the database user registry on Solaris
After creating and using the database user registry, we can run wp-update-db to update the database user ID, password, and/or the database where the data is stored. This task does not change the DN structure stored in the database repository.In a clustered environment, start the dmgr and nodeagent and verify they are able to synchronize.
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 before running wp-update-db. See Set up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin commands for information about setting up a VMM database. After populating the new database with the VMM tables and creating the data sources, restart the WebSphere_Portal server.
If we are changing the database administrator password, complete the steps in Change database passwords used by WebSphere Portal before running wp-update-db.
Update the database user registry in the default federated repository
To help ensure correct properties, we can use...
WP_PROFILE/ConfigEngine/config/helpers/wp_add_DB.properties
- Edit wkplc.properties
- Update the value for the following required parameters in wkplc.properties under the Federated DB repository heading:
federated.db.DataSourceName
federated.db.DbType
federated.db.DbUrl
federated.db.id
federated.db.DbUser
federated.db.DbPassword
- Save changes to wkplc.properties.
- Add a database user registry to the default federated repository...
./ConfigEngine.sh wp-update-db -DWasPassword=foo
- Stop and restart servers, dmgrs, and node agents.
If you created the clustered environment, including the additional nodes, and then completed the steps in this task, run update-jcr-admin on the secondary nodes.
Parent: Update the user registry on Solaris
Related:
Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation