This topic provides a general overview of migrating from a Lotus® Expeditor 6.1.x Server system to Lotus Expeditor Server 6.2.
The migration strategy for moving a Lotus Expeditor Server 6.1.x to Lotus Expeditor Server 6.2 involves installing and configuring a working Lotus Expeditor Server 6.2 system that is parallel to your existing Lotus Expeditor Server 6.1 system and then migrating the desired data from the 6.1 system into the 6.2 system using the tools and documentation provided with the 6.2 system. The Lotus Expeditor Server 6.1 system data will not be modified in any way that would prevent it from working or attempting the Lotus Expeditor Server 6.1 to Lotus Expeditor Server 6.2 migration again. You can repeat the migration several times if necessary. Repeating allows you the opportunity to test the migration before you complete the final migration to permanently move to the new Lotus Expeditor Server 6.2 system.
Migration is supported from Lotus Expeditor Server 6.1 and Lotus Expeditor Server 6.1.1. If you are Lotus Expeditor Server 6.1, there is no requirement that you first upgrade to version 6.1.1 before migrating. In general, throughout this document, the existing Lotus Expeditor Server is referred to as Lotus Expeditor Server 6.1.x. This refers to both the 6.1 and 6.1.1 versions.
You can migrate all components of Lotus Expeditor Server with the exception of MQ Everyplace® and WebSphere® Member Manager. Migration of MQ Everyplace requires you to redeploy your MQ Everyplace application on the Lotus Expeditor Server 6.2 system. This requires you to recreate any MQ Everyplace queues you created on your Lotus Expeditor Server 6.1 system on your new Lotus Expeditor Server 6.2 system. WebSphere Application Server 6.1 provides the successor to WebSphere Member Manager, called WebSphere Identity Manager (WIM). Although similar, it is not possible to migrate the WMM configuration from Lotus Expeditor Server 6.1 to the VIM configuration in WebSphere Application Server 6.1.
Migration from a Lotus Expeditor Server 6.1 system to a Lotus Expeditor Server 6.2 system can only occur when the environments for each system are similar. The following lists aspects of each system that must be similar to achieve successful migration:
- Operating system - You can only migrate from similar operating systems. The target operating system can be a higher level of the same operating system.
- User registry - You must use the same user registry for the Lotus Expeditor Server 6.2 as you used for the Lotus Expeditor Server 6.1.
- Database user registry - If your current Lotus Expeditor Server v6.1 uses the database user registry, there is no support for migrating this registry to Lotus Expeditor Server 6.2 environment. WebSphere Application Server v6.1 provides an integrated file-based user registry that is not compatible with the WebSphere Member Manager registry deployed with Lotus Expeditor Server 6.1. You will be unable to migrate the 6.1 environment, including data from DB2® Everyplace and Device Manager Server, to a Lotus Expeditor Server 6.2 system.
- LDAP - If your Lotus Expeditor Server 6.1 has been reconfigured to use an Active Directory 2003 LDAP user registry or some other LDAP user registry, then the WebSphere Application Server v6.1 environment, in which Lotus Expeditor Server 6.2 system will be installed, must be reconfigured to use the same LDAP user registry before proceeding with migration of data. Migration from one LDAP user registry to another is not supported.
- Userid and groups - 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 server to ensure successful migration.
- Databases - You must migrate from a similar database. For example, you cannot migrate from DB2 9.1 to Oracle.
Parent topic: Migrating from Lotus Expeditor Server 6.1.x to 6.2: XPD621