Review the following information to successfully plan your migration from Lotus® Expeditor Server 6.1.x to Lotus Expeditor Server 6.2.
The following sections includes information you need to prepare for migrating to Lotus Expeditor Server 6.2. Important: You must use the same userid and groups for the Lotus Expeditor Server 6.2 as you used for the Lotus Expeditor Server 6.1 to ensure successful migration.
Review which components to migrate
In Lotus Expeditor Server 6.1, all components were installed and configured. In Lotus Expeditor Server 6.2, you can choose which components to install and configure. Therefore, you may not need to migrate all components. In addition, your usage of a component can influence whether or not to migrate the existing data.
- See Migrate DB2® Everyplace® data to determine whether you need to migrate DB2 Everyplace data.
- See Migrate Client Management Services data to determine whether you need to migrate Client Management Services data.
Plan on remote database support
Lotus Expeditor Server 6.2 only supports clustering if it is configured using a remote database server. If you intend to migrate from a 6.1 system and then cluster it, you must configure the Lotus Expeditor Server 6.2 environment for a remote DB2 server. You may only cluster your 6.2 system after the final migration is complete.
Understand LDAP User Registry support
Lotus Expeditor Server 6.2 support for LDAP user registries has significantly changed from prior releases. In previous releases, Lotus Expeditor Server integrated a technology component called WebSphere® Member Manager. This component provided the interface with customer LDAPs. In addition, the install process for Lotus Expeditor Server always started with the deployment of a database user registry. The process of configuring with a customer's LDAP user registry was a guided, post-installation step.
Lotus Expeditor Server 6.2 introduces support for WebSphere Application Server 6.1. WebSphere Application Server 6.1 integrates a virtual member manager support as part of its federated repositories support. This support supersedes the support provided by Lotus Expeditor Server 6.1. All of the configuration to enable integration with a customer's LDAP is now part of WebSphere Application Server configuration. WebSphere Application Server provides a default, file-based registry that replaces the database user registry previously setup by Lotus Expeditor Server 6.1. Before starting the migration process, you should review configuring and managing federated repositories in the WebSphere Information Center at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/twim_managing_realm.html
Similar to earlier releases, to migrate Lotus Expeditor Server 6.1 to Lotus Expeditor Server 6.2, they both must be configured to use the same external registry. The WebSphere Application Server 6.1 environment must be configured with the external registry before attempting to migrate the data from a Lotus Expeditor Server 6.1 system. The Lotus Expeditor Server 6.2 migration process does not migrate the user registry configuration settings. A Lotus Expeditor Server 6.1 system configured with the local database registry cannot be migrated to a Lotus Expeditor Server 6.2 system.
Review unsupported scenarios
Migration is not supported in the following scenarios:
- In place, same system migration or upgrade.
- Migration from any WebSphere Everyplace Access system.
- Migration to a Lotus Expeditor Server 6.2 system that is configured to a different LDAP server than the Lotus Expeditor Server 6.1 system.
- Migration from a Lotus Expeditor Server 6.1 system that is configured with the local database user registry.
- Migration from WebSphere Everyplace Deployment 6.0.
- Migration to an operating system different than that of the Lotus Expeditor Server 6.1.
- Migration to an database different than that of the Lotus Expeditor Server 6.1.
- Migration from a beta release of IBM® Lotus Expeditor Server 6.2.
Parent topic: Migrating from Lotus Expeditor Server 6.1.x to 6.2: XPD622