Portal, V6.1

---

 

Update a group member on Windows

After creating your LDAP user registry, you may find that your group member is not correct. You can update the group member in your LDAP user registry configuration. Ensure that the server1 and WebSphere_Portal servers are started before starting this task.

Perform the following steps to update the group member in your LDAP user registry:

1. Optional

   Run...

   ./ConfigEngine.sh wp-query-repository -DWasPassword=wpsadmin

   ...from WP_PROFILE/ConfigEngine directory to list the names and types of configured repositories.

2. Edit wkplc.properties located inWP_PROFILE\ConfigEngine\properties.

3. Enter a value for the following required parameters in the wkplc.properties file under the VMM LDAP group member attribute configuration heading:

   • gm.ldap.id

   • gm.groupMemberName

   • gm.objectClass

   • gm.scope

   • gm.dummyMember

4. Save changes to the wkplc.properties file.

5. Run the ConfigEngine.bat wp-update-ldap-groupmember -DWasPassword=wpsadmin

   ...from WP_PROFILE\ConfigEngine directory to update the group member information for your LDAP user registry or to create the group member if it does not exist.

6. To propagate the security changes:

   Option	Description
   Stand-alone environment	cd WP_PROFILE/bin ./stopServer.sh server1 -username adminid -password passwd ./stopServer.sh WebSphere_Portal -username adminid -password passwd ./startServer.sh server1 ./startServer.sh WebSphere_Portal
   Clustered environment	cd dmgr_profile_root\bin ./stopManager.sh cd WP_PROFILE/bin ./stopNode.sh -username adminid -password passwd ./stopServer.sh server1 -username adminid -password passwd ./stopServer.sh WebSphere_Portal -username adminid -password passwd cd dmgr_profile_root\bin ./startManager.sh cd WP_PROFILE/bin ./startNode.sh ./startServer.sh server1 ./startServer.sh WebSphere_Portal

 

Parent topic

Updating your user registry on Windows

---