Update the base entry on Windows

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 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.bat wp-update-base-entry -DWasPassword=password task, from the profile_root/ConfigEngine directory, to update a base entry in a repository.
   • Propagate the security changes:

     Option	Description
     Standalone	cd profile_root/bin stopServer.bat server1 -username admin_userid -password admin_password cd profile_root/bin stopServer.bat WebSphere_Portal -username admin_userid -password admin_password cd profile_root/bin startServer.bat server1 cd profile_root/bin startServer.bat WebSphere_Portal
     Cluster	cd dmgr_profile/bin stopManager.bat-username admin_userid -password admin_password cd profile_root/bin stopNode.bat-username admin_userid -password admin_password cd profile_root/bin stopServer.bat WebSphere_Portal -username admin_userid -password admin_password cd dmgr_profile/bin startManager.bat cd profile_root/bin startNode.bat cd profile_root/bin startServer.bat 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 Windows

Related tasks

Enable LDAP security after cluster creation

---