Update the stand-alone LDAP user registry on HP-UX


Overview

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 rerunning the wp-modify-ldap-security task to change the LDAP repositories or because the task failed, choose a new name for the realm using the standalone.ldap.realm parameter or set ignoreDuplicateIDs=true in wklpc.properties..


Update the standalone LDAP user registry

To update, you can use...

  1. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  2. To identify the stand-alone LDAP user registry that you want to update, set the following parameter in wkplc.properties under the Stand-alone LDAP repository...

  3. Update the following parameters in wkplc.properties under the Stand-alone LDAP repository heading:

  4. Save changes to wkplc.properties.

  5. Validate the LDAP server settings...

      ./ConfigEngine.sh validate-standalone-ldap -DWasPassword=password

    Note that if you have not deleted the default file repository, WasPassword is the value entered during installation and not a value found in your LDAP user registry.

  6. Update the standalone registry...

    1. Run...

        cd profile_root/bin
        ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password

    2. Run...

        cd profile_root/ConfigEngine
        ./ConfigEngine.sh wp-update-standalone-ldap -DWasPassword=password

  7. 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
    ./startManager.sh
    cd profile_root/bin
    ./startNode.sh
    ./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 an HP-UX


Related tasks


Enable LDAP security after cluster creation