Restore the VMM setup with a federated file repository on Linux
If the business needs change or something happens to make the user registry configuration inoperable, we can run the task...wp-restore-default-repository-configuration
...to restore the default VMM setup with a federated file repository. 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.
Restore the default VMM setup with a federated file repository
- Edit wkplc.properties
- Set the following required parameters 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.
- Restore the default repository...
./ConfigEngine.sh wp-restore-default-repository-configuration -DWasPassword=foo
- Stop and restart servers, dmgrs, and node agents.
- Optional. Restore the default repository...
./ConfigEngine.sh wp-restore-default-repository-add-group-member -DgroupUniqueName=value -DmemberUniqueName=value
Where the value for DgroupUniqueName is the value specified for the following parameter in wkplc.properties: restore.file.primaryPortalAdminGroup. The value for DmemberUniqueName is the value specified for restore.file.primaryAdminId in wkplc.properties.
- Stop and restart servers, dmgrs, and node agents.
If you created the clustered environment, including the additional nodes, and then completed the steps in this task, run update-jcr-admin on the secondary nodes.
Parent: Manage the user registry on Linux
Related:
Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation