Document manager: migrate from 5.1.x to 6.0

 

+

Search Tips   |   Advanced Search

 

Use the following steps to migrate Document Manager from Portal v5.1.x to Portal v6.0. Before migrating, 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.1.x migration, any access roles on the ICM_CONTENT_REPOSITORY virtual resource on the 5.1 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. Verify that the 5.1.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. Configure the Document Transfer Tool on the 5.1.0.x WebSphere Portal server, as follows:

    1. Install PK18903.

    2. Install portal_server_root/jcr/installableApps/icmjcr.ear to WebSphere Portal, or to the Portal cluster if in a clustered environment, using the administrative console.

    3. If in a clustered environment, update the Web server plugin and restart the Web server.

    4. Restart WebSphere Portal, or the Portal cluster.

  3. Create an empty export directory on the 5.1.x system. For example, c:\export\. Share this directory with the 6.0 system (sharing can be implemented with net use or NFS mount, etc.). This export directory will be used for the MigDirSource property, described below.

  4. Update the file portal_server_root/jcr/migration/conf/pdm_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 on the source (5.1.x) server. This directory will be used for export from 5.1.x. Verify that this directory is empty and can be shared with the 6.0 server.

      • MigDirSourceShared: The shared directory on the target (6.0) server. The tasks after the export task need to access the exported data from the target (6.0) server. Either the target server maps to the source directory, or the exported data must be copied to the target server's local directory. If the source directory is shared, this property is the source directory as it appears on the target (6.0) server. If the exported data are copied to the target server, this property is the local directory where exported data are stored.

      • 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.

      • SourceServerPort: The host.name and port for the 5.1.x server. By default, the port for the 5.1.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.

      • DocLib: The list of Document Libraries to migrate, separated by commas (e.g. "Document Manager" or "Document Manager, MyLib").

      • ExportUserId: Set this value to the 5.1.x Portal administrator user ID. If LDAP security is enabled, this needs to be a fully qualified DN.

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

      • ImportUserId: Set this value to the 6.0 Portal administrator user ID. If LDAP security is enabled, this needs to be a fully qualified DN.

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

      • IncludeWorkflow: Change to true to migrate the workflow information, including submitted drafts.

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

      • AddWorkspace: Comma-separated additional workspaces (if more than one) to be added for migration.

  5. Edit the jcrmig.properties file in the portal_server_root/migration/components/jcr directory. Modify the appServerDir property to specify the location of the WebSphere Application Server on the target (6.0) server.

  6. Start both 5.1.x and 6.0 Portal servers.

  7. Make sure you are in the portal_server_root/migration/ directory, then run WPmigrate.bat/sh migrate-pdm-export-51x.

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

    2. Verify that the export directories were populated correctly.

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

    1. Verify that this migration step completed without errors.

    2. Verify that the import directories were populated correctly.

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

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

 

Parent topic:

Migrating additional components