Restoring the VMM setup with a federated file repository on AIX
If your business needs change or something happens to make the user registry configuration inoperable, you can run the wp-restore-default-repository-configuration task to restore the default VMM setup with a federated file repository, which will allow you to reconfigure the user registry to meet your business needs. The task deletes all existing repositories, creates a new realm, and configures a file repository in VMM. The task also creates a new user and a new user group, which is set to portal and WAS administrators.
Perform the following steps to restore the default VMM setup with a federated file repository:
- Edit...
profile_root/ConfigEngine/properties/wkplc.properties
- Set the following parameters in wkplc.properties under the Restore VMM security heading:
- restore.file.realm
- restore.file.delimiter
- restore.file.primaryAdminId
- restore.file.primaryAdminPassword
- restore.file.primaryPortalAdminGroup
- Save changes to wkplc.properties.
- Run...
./ConfigEngine.sh wp-restore-default-repository-configuration -DWasPassword=password
from the profile_root/ConfigEngine directory, to restore the default repository.
- Propagate the security changes:
Option Description Standalone
- cd profile_root/bin
./stopServer.sh server1 -username admin_userid -password admin_password- cd profile_root/bin
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password- cd profile_root/bin
./startServer.sh server1- cd profile_root/bin
./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- cd profile_root/bin
./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password- cd dmgr_profile/bin
./startManager.sh- cd profile_root/bin
./startNode.sh- cd profile_root/bin
./startServer.sh WebSphere_Portal
- Run...
./ConfigEngine.sh wp-restore-default-repository-add-group-member -DWasPassword=password
...taskto restore the default repository.
- 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_PortalCluster 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 the enable-jcr-security task on the secondary node; see Enabling LDAP security after cluster creation.
Parent topic:
Manage the user registry on AIX