After adding your user registry, you may find that you
need to update a single entity type with the value of the default
parent. For example, if you delete a repository, you will need to
update the entity type if it points to the deleted 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 an entity
type:Procedure
- Use a text
editor to open the wkplc.properties file, in
the wp_profile_root\ConfigEngine\properties directory.
- Enter the following parameters
in the wkplc.properties file under the VMM supported
entity types configuration heading:
Note: See the properties
file for specific information about the advanced parameters.
- entityTypeName
- defaultParent
- rdnProperties
- Save your changes to
the wkplc.properties file.
- Choose one
of the following tasks to update your entity type:
- To add a new entity type to the existing
list
- Run the ConfigEngine.bat wp-update-entitytype -DWasPassword=password task,
from the wp_profile_root\ConfigEngine directory.
- To delete the old entity types before
adding the new RDN attribute as the only entry in the RDN list
- Run the ConfigEngine.bat wp-set-entitytype -DWasPassword=password task,
from the wp_profile_root\ConfigEngine directory.
- 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.