You may need to update a single entity type with the value of the default parent.

For example, if you delete a repository, update the entity type if it points to the deleted repository.

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.

Update an entity type

If you are changing the existing rdnProperties value, perform this task twice; once to clear the current rdnProperties value and once to add the new value.

  1. Edit...


  2. Enter the following parameters under the VMM supported entity types configuration heading:

  3. Save changes to wkplc.properties.

  4. Update your entity type:

    Option Description
    Add a new entity type to the existing list Run...

      ConfigEngine.sh wp-update-entitytype -DWasPassword=password task, from the profile_root/ConfigEngine directory.
    Delete the old entity types before adding the new RDN attribute as the only entry in the RDN list Run...

      ConfigEngine.sh wp-set-entitytype -DWasPassword=password task, from the profile_root/ConfigEngine directory.

  5. Propagate the security changes:

    Option Description
    Standalone cd profile_root/bin
    ./stopServer.sh server1 -username admin_userid -password admin_password
    ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
    ./startServer.sh server1
    ./startServer.sh WebSphere_Portal
    Cluster cd dmgr_profile/bin
    ./stopManager.sh-username admin_userid -password admin_password
    cd profile_root/bin
    ./stopNode.sh -username admin_userid -password admin_password
    ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
    cd dmgr_profile/bin
    ./startManager.sh cd profile_root/bin
    ./startServer.sh WebSphere_Portal

If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.

Parent topic:

Updating the user registry on i5/OS

Related tasks

Enable LDAP security after cluster creation