Update the federated LDAP user registry on i5/OS

You can update the default federated repository to change...

The task wp-update-federated-ldap does not modify...

See the separate tasks for updating these parameters.

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.

To ensure correct properties, use the helper file...

  1. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  2. Enter the following parameters under the Federated LDAP repository heading ...

  3. Update the following parameters in wkplc.properties under the Federated LDAP repository heading:

  4. Save changes to wkplc.properties.

  5. Run...

      ConfigEngine.sh validate-federated-ldap -DWasPassword=password task to validate your LDAP server settings.

      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.

    • Run...

        ConfigEngine.sh wp-update-federated-ldap -DWasPassword=password task, from the profile_root/ConfigEngine directory, to update the LDAP user registry in the default federated repository.

        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 i5/OS


Related tasks


Enable LDAP security after cluster creation