After you create
your base entries, you might need to update the distinguished name
(DN) in the repository that uniquely identifies the base entry name.
This task applies only to federated repository configurations. This
task does not update the base DN entry if you use a stand-alone repository.
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 and verify that they are able to synchronize.
About this task
Complete the following steps to update the base
entry:Procedure
- Use a text
editor to open the wkplc.properties file, in
the wp_profile_root\ConfigEngine\properties directory.
- Enter a value
for the following parameters in the wkplc.properties file
under the VMM repository base entry configuration heading. To create
more base entries within the LDAP user registry to use, when you create
realms:
- id
- baseDN
- nameInRepository
- Save your changes to
the wkplc.properties file.
- Run the ConfigEngine.bat
wp-update-base-entry -DWasPassword=password task,
from the wp_profile_root\ConfigEngine directory
to update a base entry in a repository.
- Stop and restart the appropriate servers
to propagate the changes. For specific instructions, see Starting and stopping servers, deployment managers, and node agents.
What to do next
If you
created your clustered environment, including the additional nodes,
and then completed the steps in this task, you must now run the update-jcr-admin task
on the secondary node. See the related links section for instructions.