Verify the migration tasks

 

+

Search Tips   |   Advanced Search

 

Prior to verifying the migration tasks, make sure that all manual migration steps are completed. Then use the steps described here to verify the success of the migration tasks.

To perform the steps below, log in to the IBM WebSphere Portal Administrative Interface for the new portal installation unless otherwise noted.

1. Verify migration of Notes and Domino Web Access (iNotes) portlets.

   1. Under Portlet Management, click Portlets. The portlet list includes an entry for each portlet that existed in the previously installed version.

   2. Select each migrated portlet, click Configure portlet, and verify that the portlet settings were migrated correctly.

      If you migrated pages that had Notes portlets in them, the portlets should be on the page after migration and should work as they did in the earlier version.

      In some previous versions of WebSphere Portal, these portlets were individual portlets, while in the current version, they are copies of one portlet.

2. Verify migration of portal clients.

   1. Under Portal Settings, click Supported Clients.

   2. Verify that the portal clients that you migrated appear in the list of supported clients.

   3. Select each migrated client, click Edit selected client, and verify that all settings for the client were migrated.

   4. Verify that your migrated clients are able to access WebSphere Portal.

3. Verify migration of user customizations.

   User customizations are attributed to a portal user who has edit but not manage permissions on a page, and are created when such a user changes the layout of a page or edits portlet settings.

   1. Log in to the new WebSphere Portal using the credentials of users who implemented the customizations.

   2. Verify that all user customizations from the earlier version are present in the new version.

      You can also pick users at random and ensure that they see the correct customizations in the new version by visually comparing the customizations in the new version with those in the earlier version.

4. Verify migration of credential vault segments and slots.

   1. Under Access, click Credential Vault.

   2. Use the Manage vault segments and Manage system vault slots options, verify that credential segments and slots from the earlier version are now also present in the new version.

5. Verify migration of themes and skins.

   1. Under Portal user interface, click Themes and Skins.

   2. Verify that the themes and skins that are listed are the ones that you migrated from the earlier version.

   3. Verify that you are able to associate migrated themes and skins to existing pages and portlets, and that they produce the required view.

6. Verify migration of portlet applications.

   1. Under Portlet Management, click Applications.

   2. Verify that the portlet applications that are listed are the ones that you migrated from the earlier version.

   3. For each Web module, verify that all your portlet applications also display in the Portlet Applications list.

   4. For each portlet application that is migrated and for which you have set up parameters on the earlier version, click Edit portlet application and verify that the parameters were migrated correctly.

7. Verify the access control for migrated portlet application and portlets.

   1. Under Access, click Resource Permissions and select Portlet Applications from the listed resource types.

   2. Click Assign Access to verify the access control information.

   3. Under Access, click Resource Permissions and select Portlets from the listed resource types.

   4. Click Assign Access to verify the access control information.

   After migration is complete, you use the XML Configuration Interface to perform a full export of the current version and verify that the roles in the exported XML file are correct.

8. Verify migration of portlet configuration data.

   1. Under Portlet Management, click Portlets.

   2. To verify that each portlet's configuration data was migrated from the earlier version, select the portlet from the list and click Configure portlet.

9. Verify migration of virtual resources.

   1. Under Access, click Resource Permissions.

   2. Select Virtual Resources from the list of resource types.

   3. Verify that all virtual resources migrated from the earlier version are present in the new version.

10. Verify migration of pages.

11. If you migrated from WebSphere Portal V6.0.1.x and your portal environment security uses IBM WAS standalone, ensure that both portal environments use the same external ID:

    (extID): <config:externalIdAttributes name="distinguishedName"/>

    1. On the earlier portal, check how extID is defined in...

       portal_server_root/wmm/wmmLDAPServerAttributes.xml

    2. On the new portal, check how extID is defined in WP_PROFILEcells/cell/wwimconfig.xml by looking at config:externalIdAttributes inside config:repositories xsi:type="config:LdapRepositoryType".

 

Parent topic

Migrating WebSphere Portal