Home

 

Migration strategies

There are different strategies for migrating to Lotus Connections 2.5 and you need to choose one that suits your topology, resources, and schedules.

 

Migration strategies

The migration strategy that you choose depends on the size of your deployment, the downtime that you can tolerate, and your hardware environment.

The following two strategies are the most common choices: Minimum down-time

  1. Install the supporting software (including WebSphere Application Server 6.1.0.23) on new hardware

  2. Stop Lotus Connections 2.0.1

  3. Complete the following steps simultaneously:

    • Update your databases to release 2.5, using the in-place procedure

    • Install Lotus Connections 2.5 and migrate Lotus Connections 2.0.1 configuration settings and content stores to release 2.5

  4. Update the URLs to point to the new deployment.
Hardware efficiency

  1. Stop Lotus Connections 2.0.1

  2. Back up Lotus Connections 2.0.1

  3. Export Lotus Connections 2.0.1 data and configurations

  4. Uninstall Lotus Connections 2.0.1

  5. Update your databases to release 2.5

  6. Update WebSphere Application Server to 6.1.0.23

  7. Install Lotus Connections 2.5, using the same configuration as your release 2.0.1 deployment

  8. Import Lotus Connections 2.0.1 data and configurations to Lotus Connections 2.5.

For more detailed information, see the Migrating a stand-alone deployment and Migrating a network deployment topics.

 

Migration path

Choose a migration path that is applicable to the version of Lotus Connections in your current deployment. If your current release is 2.0.1, update it to release 2.5. If you are using an earlier release than 2.0.1, update it to the succeeding release before finally updating to release 2.5. For example:


Migrating to Lotus Connections 2.5

 

Related tasks

Migrating a stand-alone deployment

Migrating a network deployment

 

Related reference


Lotus Connections detailed system requirements


+

Search Tips   |   Advanced Search