Update the realm configuration on Linux

You can update the realm configuration in the default federated 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.

Perform the following steps to update the realm configuration in the default federated repository:

1. Edit...
   profile_root/ConfigEngine/properties/wkplc.properties

2. Enter a value for the following parameters under the VMM realm configuration heading:
   • realmName
   • securityUse
   • delimiter

3. Save changes to wkplc.properties.

4. Run...
   ./ConfigEngine.sh wp-update-realm -DWasPassword=password

   from the profile_root/ConfigEngine directory, to update a realm configuration.

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 ./startNode.sh ./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 Linux

Related tasks

Enable LDAP security after cluster creation

---