Enabling LDAP security after cluster creation

If you set or changed your security configuration after you created your clustered environment, you will need to update the security configuration on all secondary nodes by updating the wkplc.properties file and running the update-jcr-admin task.

Before you begin

You configured your clustered environment and then configured security or updated your security configuration.

Procedure

  1. Update the wkplc.properties file, located in the wp_profile_root/ConfigEngine/properties directory, on each secondary node in the cluster with the same user registry information you used to configure the primary node.
    z/OS only: Open a UNIX System Services (z/OS UNIX System Services) command prompt.
  2. Update the wkplc.properties file on the secondary node, with the correct value for the PortalAdminId parameter.
    Attention: Use the fully qualified administrator name; for example, uid=wpsadmin,o=defaultWIMFileBasedRealm.
  3. Save your changes to the wkplc.properties file.
  4. Run the following task from the wp_profile_root/ConfigEngine directory on each secondary node to update the security configuration:
    Table 1. Task to update the security configuration on the secondary node.
    Operating system Task
    Windows ConfigEngine.bat update-jcr-admin -DWasPassword=password
    AIX®SolarisLinux ./ConfigEngine.sh update-jcr-admin -DWasPassword=password
    IBM® i ConfigEngine.sh update-jcr-admin -DWasPassword=password
    z/OS® ConfigEngine.sh update-jcr-admin -DWasPassword=password
  5. Restart the cluster member on each additional node.