Migrating a stand alone server
By following the steps laid out in this section, you can migrate to Lotus Quickr 8.5.
Migration from version 188.8.131.52 to 8.5 is performed using parallel migration. In a parallel migration, each system is deployed separately and the data is migrated from the older system to the newer one. You can have 184.108.40.206 and 8.5 deployed either on the same or different systems. Except for fixes and configuration changes required to enable migration, the 220.127.116.11 environment is left intact.
An upgrade from a previous version to 8.5 is not supported due to the underlying change to IBM® WebSphere® Application Server 6.1 and IBM WebSphere Portal 6.1.5. In an upgrade the runtime and the data is updated. For example, going from Lotus Quickr 8.1 to Lotus Quickr 8.1.1 is an upgrade.
Migrating a cluster
Migrating directly to a cluster is not supported. Instead, follow the steps to migrate to a IBM Lotus Quickr 8.5 stand alone server and then deploy the cluster. Consider the following when migrating a clustered environment:
- Migrate the primary node from the source Lotus Quickr environment. Migrating a secondary node can lead to security problems.
- Unless you are implementing a custom user registry, migrate to a new cell. Do not attempt to federate a migrated node into an existing cell. If you are implementing a custom user registry, you can federate into an existing cell that matches the implementation of you custom user registry.
- The WebSphere Application Server node name for the target server must be the same as the name for the managed node of the source server. If you have already installed Lotus Quickr and did not specify the same node name during installation, you can change the node name. For detailed instructions, see the procedure for altering the node name property for a standalone Base profile in Best Practices for Configuration Changes in WebSphere Application Server v6.x.
Parent topic: Planning for migration: qp85
Next topic: Supported migration paths: qp85
Best Practices for Configuration Changes in WebSphere Application Server v6x