The initial federated repositories setup might not include the advanced set up for the
group membership attribute. You can configure the group membership attribute after the initial
setup. Specify the properties in the wkplc.properties file and
then run the wp-create-ldap-groupconfig task manually.
Before you begin
In a stand-alone server environment, you can complete the
following task when the servers are either stopped or started. In
a clustered environment, start the deployment manager and node agent.
Then, verify that they are able to synchronize.Procedure
- Go to the wp_profile_root/ConfigEngine/properties directory.
- Open the wkplc.properties file with a text editor.
- Update the following parameters in the wkplc.properties
file under the VMM LDAP group member config heading:
Note: Go to the properties file for specific information about the parameters.
- gc.ldap.id
- gc.name
- gc.updateGroupMembership
- gc.scope
- Open a command prompt.
- Change to the wp_profile_root/ConfigEngine directory.
- Run the following task to update the group membership for
the LDAP user registry:
- AIX®
HP-UX
Linux
Solaris: ./ConfigEngine.sh wp-create-ldap-groupconfig
-DWasPassword=password
- IBM® i: ConfigEngine.sh wp-create-ldap-groupconfig
-DWasPassword=password
- Windows: ConfigEngine.bat wp-create-ldap-groupconfig
-DWasPassword=password
- Stop and restart the appropriate servers to propagate the
changes. For instructions, go to Starting and stopping servers, deployment managers, and node agents.