Document manager: migrate from 5.0.x to 6.0

 

+

Search Tips   |   Advanced Search

 

Use the following steps to migrate Document Manager from Portal v5.0.x to Portal v6.0. Before migrating, apply the migration fix patch to the 5.0.x Portal. The patch is under APAR PK16482. In addition, you should 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. For 5.0.x 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 target server.

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

When you migrate Document Manager from Portal v5.0.x to Portal v6.0, all document libraries are migrated at the same time. Verify that the 5.0.x server is running a supported Portal version for migration to v6.0. The supported Portal versions are listed at Planning.

  1. Required: Ensure that you completed the steps in 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 system. Confirm that the following properties in the <init> section are set as specified, modifying the properties if necessary:

    • init

      MigDirSource The migration directory for the exported data. This directory will be used for export and conversion from 5.0.x. Verify that this directory is empty. Note that this directory is on the target (6.0) server.
      MigDirTarget The migration directory on the target (6.0) server. This directory will be used for import to 6.0. Verify that this directory is empty and is different from the MigDirSource.
      Database50 Set to the type of database server on the 5.0x server (such as db2, cloudscape, oracle, or sqlserver).
      SourceServerPort The host.name and port for the 5.1.x server. By default, the port for the 5.0.x server is 9081.
      TargetServerPort The host.name and port for the 6.0 server. By default, the port for the 6.0 server is 10038.
      ExportUserId Set this value to the 5.0.x Portal administrator user ID.
      ExportPassword Change if not the correct value for the 5.0.x administrator password.
      ImportUserId Set this value to the 6.0 Portal administrator user ID.
      ImportPassword Change if not the correct value for the 6.0. 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 system.

  4. Edit...

    portal_server_root/migration/components/jcr/jcrmig.properties

    Modify the appServerDir property to specify the location of the WebSphere Application Server.

  5. Start both 5.0.x and 6.0 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 logs for extended diagnostic information.

Document Manager migration from Portal v5.0.x to Portal v6.0 does not migrate any drafts or tasks, but will only migrate approved or finalized documents.

 

Parent topic:

Migrating additional components