Restoring the VMM setup with a federated file repository on i5/OS

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:

  1. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  2. Set the following parameters in wkplc.properties under the Restore VMM security heading:

  3. Save changes to wkplc.properties.

  4. Run...

      ConfigEngine.sh wp-restore-default-repository-configuration -DWasPassword=password task, from the profile_root/ConfigEngine directory, to restore the default repository.

    • Propagate the security changes:

      Option Description
      Standalone

      1. stopServer server1 -username admin_userid -password admin_password

        ...from...

          profile_root/bin

      2. stopServer WebSphere_Portal -username admin_userid -password admin_password

        ...from...

          profile_root/bin

      3. startServer server1

        ...from...

          profile_root/bin

      4. startServer WebSphere_Portal

        ...from...

          profile_root/bin

      Cluster

      1. stopManager-username admin_userid -password admin_password, from the DMGR_PROFILE/bin

      2. stopNode -username admin_userid -password admin_password from the profile_root/bin directory

      3. stopServer WebSphere_Portal -username admin_userid -password admin_password

        ...from...

          profile_root/bin

      4. startManager, from the DMGR_PROFILE/bin

      5. startNode

        ...from...

          profile_root/bin

      6. startServer WebSphere_Portal

        ...from...

          profile_root/bin

    • Run...

        ConfigEngine.sh wp-restore-default-repository-add-group-member -DWasPassword=password

      ...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
      ./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:

Manage the user registry on i5/OS


Related tasks


Enable LDAP security after cluster creation