Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

---

 

Document manager: migrate from 5.0 to 6.0.x

Use the following steps to migrate Document Manager from Portal version 5.0 to Portal version 6.0.x.

Before migrating, do the following:

• Apply the migration fix patch to your 5.0 portal. The patch is under APAR PK16482, located at this path on the portal server: portal_server_root/migration/fixes/5022.

• Synchronize Document Manager global access settings. Global access settings for document library inheritance might be different between the source and target servers. Since the scope of migrated settings does not include global settings, synchronize the settings between the source and target servers so that access control for document libraries remains the same after migration. Any access roles on the WPCP virtual resources on the 5.0 source server should also be set on the content root of the 6.0.x target server.

• Manually set the locks, workflow and version settings for the target default document library. When migrating, portal access settings for the default document library such as locks, workflow activity and versions, are not imported to the 6.0.x server.

• Verify that your 5.0 server is running a supported Portal version for migration to version 6.0.x. The supported Portal versions are listed at Planning migration.

• Migrate all users and groups before migrating Document Manager information. Make sure that the administrative user (default is wpsadmin) is added to the Content Contributor group on the 5.0 portal server. The Content Contributor group may not exist in the 5.0 portal server. If it does not, simply create the group and add the administrative user to the group. When creating the group, no special access needs to be assigned, just creating the group is sufficient.

When you migrate Document Manager from Portal version 5.0 to Portal version 6.0.x, all document libraries are migrated at the same time.

1. Required: Ensure that you completed the steps in Preparing to run the migration tasks and Migrating WebSphere Portal Configurations. Step 1 must be completed before continuing the Document Manager migration process. Migrating Document Manager data without performing this step is not supported.

2. Update the file portal_server_root/jcr/migration/conf/pdm50_conf.xml on the Portal 6.0.x system. Confirm that the following properties in the <init> section are set as specified, modifying the properties if necessary:

   • init

     • MigDirSource: The migration directory on the target (6.0.x) server for the exported data. This directory will be used for export and conversion from 5.0 and must be empty.

     • MigDirTarget: The migration directory on the target (6.0.x) server for the imported data. This directory will be used for import to 6.0.x and must be empty. Make sure that this directory is different from the MigDirSource directory.

     • Database50: Set to the type of database server on the 5.0 server (such as DB2, Oracle, or SQLserver).

     • SourceServerPort: The host name and port for the 5.0 server. By default, the port for the 5.0 server is 9081.

     • TargetServerPort: The host name and port for the 6.0.x server. By default, the port for the 6.0.x server is 10038.

     • ExportUserId: Set this value to the 5.0 Portal administrator user ID.

     • ExportPassword: Change if not the correct value for the 5.0 administrator password.

     • ImportUserId: Set this value to the 6.0.x Portal administrator user ID.

     • ImportPassword: Change if not the correct value for the 6.0.x administrator password.

     • IncludeVersion: Change to true to migrate the document versions.

3. Copy portal_server_root/shared/app/pcm.jar from the Portal 5.0 system to portal_server_root/jcr/migration/lib on the Portal 6.0.x system.

4. Edit the jcrmig.properties file in the portal_server_root/migration/components/jcr directory on the Portal 6.0.x system. Modify the appServerDir property to specify the app_server_root location on the Portal 6.0.x system.

5. Start both 5.0 and 6.0.x Portal servers.

6. Run WPmigrate.bat/sh migrate-pdm-export-50x.

   1. Verify that this migration step completed without errors. If any errors occurred, check the Portal 5.0 logs for extended diagnostic information.

   2. Verify that the export directory was populated correctly.

7. Run WPmigrate.bat/sh migrate-pdm-convert-50x.

   1. Verify that this migration step completed without errors.

   2. Verify that the output directory from the conversion is populated correctly.

8. Run WPmigrate.bat/sh migrate-pdm-transform-50x.

   1. Verify that this migration step completed without errors.

   2. Verify that the output directory from transform is populated correctly.

9. Run WPmigrate.bat/sh migrate-pdm-import-50x.

   1. Verify that this migration step completed without errors. If any errors occurred, check the Portal 6.0.x logs for extended diagnostic information.

The previous level Document Manager portlet is not migrated, although there is a new Document Manager portlet that is provided with the current system. Any portal pages that previously displayed the Document Manager portlet on your old system will be missing that portlet. If the Document Manager portlet was the only portlet on a portal page, the page will still be migrated as a blank page. You can either add the current level of the Document Manager portlet to these pages, or delete the pages if they are no longer needed. If the previous level of Portal restricted the page to only contain the Document Manager portlet (like the sample Documents page does), you will need to change the properties for the page through Administration prior to being able to add the Document Manager portlet to the page.

This is done through Administration > Manage Pages > Edit Page Properties for the Documents page (by default, the one under the "My Portal" page). Under the Advanced section, there is a checked option labeled This page has a list of allowed portlets. This option can be un-checked to allow all portlets to be added to the page, or the text link can be selected to only allow specific portlets with the option still checked. If the restrictive option is chosen, the Document Manager portlet must be added to the list of specific portlets allowed on this page prior to attempting to add it. If this is not done, the Documents page will be set to inactive when an attempt is made to add a portlet that is not on this list, after receiving the following error message: Unable to add portlet to component. The portlet is not allowed on this composition. If this message is displayed and the Documents page is made inactive, use the Administration > Manage Pages option to reactivate the page after making the above changes to add the Document Manager portlet to the page.

Document Manager migration from Portal version 5.0 to Portal version 6.0.x does not migrate any drafts or tasks, but will only migrate approved or finalized documents.

 

Parent topic:

Migrating additional components

---