Change to a federated repository on Windows

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.

To ensure the correct properties are entered use the helper file...

profile_root/ConfigEngine/config/helpers/wp_security_federated.properties

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

2. Set the following parameters in wkplc.properties under VMM Federated repository properties:
   • federated.primaryAdminId
   • federated.realm
   • federated.serverId
   • federated.serverPassword

3. Save changes to wkplc.properties.

4. Run...
   ConfigEngine.bat wp-modify-federated-security -DWasPassword=password -Dskip.ldap.validation=true task, from the profile_root/ConfigEngine directory, to change the configuration to use a federated repository.

   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 Windows

Related tasks

Enable LDAP security after cluster creation

---