Update the base entry on i5/OS

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.

Update the base entry

1. Edit...
   profile_root/ConfigEngine/properties/wkplc.properties

2. Enter a value for the following parameters under the VMM repository base entry configuration heading to create additional base entries within the LDAP user registry to use when creating realms:

   • id
   • baseDN
   • nameInRepository

3. Save changes to wkplc.properties.

4. Run...
   ConfigEngine.sh wp-update-base-entry -DWasPassword=password task, from the profile_root/ConfigEngine directory, to update a base entry in a 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 the enable-jcr-security task on the secondary node; see Enabling LDAP security after cluster creation.

Parent topic:

Updating the user registry on i5/OS

Related tasks

Enable LDAP security after cluster creation

---