Update the context pool configuration on Linux
After configuring LDAP user registry, you may find that you need to adjust the number of context instances concurrently maintained by the content pool in order to increase performance.
In single server environments, you do not have to start or stop the WebSphere_Portal and server1 servers to complete the following steps. In clustered environments, stop all application servers on system, including WebSphere_Portal, then start the nodeagent and dmgr servers before you begin any of the following steps.
To update the context pool configuration:
If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.
- Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties
- Update the following required parameters in wkplc.properties under the VMM LDAP context pool heading:
cp.ldap.id
cp.maxPoolSize
- Save changes to wkplc.properties.
- Run the ./ConfigEngine.sh wp-update-ldap-contextpool -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to update the context pool configuration for the LDAP user registry.
- Stop and restart the appropriate servers to propagate the changes.
Parent
Update user registry on Linux
Related tasks
Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation