Update the database user registry on Linux

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 a single server environment the WebSphere_Portal and server1 servers can be either stopped or started.

In a clustered environment stop all appservers on the system including WebSphere_Portal and server1 and then start the nodeagent and deployment manager servers before starting the following task.

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 Setting 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 Changing 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 the profile_root/ConfigEngine/config/helpers directory, when performing this task to ensure the correct properties are entered; see Configuration task properties for information about using the helper file. In the instructions below, when the step refers to wkplc.properties, you will use your wp_add_DB.properties helper file.

  1. Edit...


  2. Update the value for the following parameters in wkplc.properties under the Federated DB repository heading:

  3. Save changes to wkplc.properties.

  4. Run...

      ./ConfigEngine.sh wp-update-db -DWasPassword=password

    from the profile_root/ConfigEngine directory, to add a database user registry to the default federated repository.

  5. Propagate the security changes:

    Option Description
    Standalone cd profile_root/bin
    ./stopServer.sh server1 -username admin_userid -password admin_password
    ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
    ./startServer.sh server1
    ./startServer.sh WebSphere_Portal
    Cluster cd dmgr_profile/bin
    ./stopManager.sh-username admin_userid -password admin_password
    cd profile_root/bin
    ./stopNode.sh -username admin_userid -password admin_password
    ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
    cd dmgr_profile/bin
    cd profile_root/bin
    ./startServer.sh WebSphere_Portal

If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.

Parent topic:

Updating the user registry on Linux

Related tasks

Enable LDAP security after cluster creation