Update the context pool configuration on HP-UX


Overview

After configuring LDAP user registry, you may find that adjust the number of context instances concurrently maintained by the content pool in order to increase performance.

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.


Procedure

To update the context pool configuration:

  1. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  2. Update the following parameters in wkplc.properties under the VMM LDAP context pool heading:

  3. Save changes to wkplc.properties.

  4. Update the context pool configuration for the LDAP user registry

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

  5. 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