Update the database user registry on i

After creating and using the database user registry, you can run the wp-update-db task 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 single server environments, you do not have to start or stop the WebSphere_Portal and server1 servers to complete the following steps. In clustered environments, stop all application servers on system, including WebSphere_Portal, then start the nodeagent and dmgr servers before you begin any of the following steps.

If you plan to change the database where data is stored, populate the new database with all necessary VMM tables and create the data sources in WAS before running the wp-update-db task. 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, please restart the server1 and WebSphere_Portal servers.

If you are changing the database administrator password, perform the steps in Change database passwords that are used by WebSphere Portal before running the wp-update-db task.

To update the database user registry in the default federated repository: Use the wp_add_DB.properties helper file, located in...

...when performing this task to ensure the correct properties are entered. In the instructions below, when the step refers to wkplc.properties, you will use wp_add_DB.properties helper file.

  1. Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties

  2. Update the value under the Federated DB repository heading:

        federated.db.DataSourceName
        federated.db.DbType
        federated.db.DbUrl
        federated.db.id
        federated.db.DbUser
        federated.db.DbPassword

  3. Save changes to wkplc.properties.

  4. Run the ConfigEngine.sh wp-update-db -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to add a database user registry to the default federated repository.

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

If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.


Parent

Update user registry on i


Related tasks


Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation

 


+

Search Tips   |   Advanced Search