Update the group membership configuration on Windows
When you configure your LDAP user registry, a group membership is automatically created. You may need to adjust the group membership configuration if you notice high loads on the LDAP server and/or long response times on authentication requests.
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.
Perform the following steps to update the group membership configuration:
- Edit...
profile_root/ConfigEngine/properties/wkplc.properties
- Update the following parameters in wkplc.properties under the VMM LDAP group member config heading:
- Save changes to wkplc.properties.
- Run...
ConfigEngine.bat wp-create-ldap-groupconfig -DWasPassword=password task, from the profile_root/ConfigEngine directory, to update the group membership for the LDAP user registry.
- 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_PortalCluster 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 Windows
Related tasks
Enable LDAP security after cluster creation