Restore the VMM setup with a federated file repository on AIX
If business needs change or something happens to make 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 user registry to meet 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.
To restore the default VMM setup with a federated file repository:
If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.
- Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties
- Required: Enter a value 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 the ./ConfigEngine.sh wp-restore-default-repository-configuration -DWasPassword=foo task, from the WP_PROFILE/ConfigEngine, to restore the default repository.
- Stop and restart the appropriate servers to propagate the changes.
- Run the following optional task to 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 you specified for the following parameter in wkplc.properties: restore.file.primaryPortalAdminGroup. The value for DmemberUniqueName is the value you specified for restore.file.primaryAdminId in wkplc.properties.
- Stop and restart the appropriate servers to propagate the changes.
Parent
Manage the user registry on AIX