Home
Migrating a pilot to a production deployment
A pilot deployment is ideal for evaluating Lotus Connections. After evaluation is complete, you can migrate the pilot deployment to a production deployment.
The migration process can be used to migrate a Lotus Connections pilot deployment to a production deployment. Migration must occur within the same release(for example, from a 2.5 pilot deployment to a 2.5 production deployment). You cannot migrate across releases.
The benefit of performing a migration is that data created by users in the course of their evaluation of Lotus Connections can be transferred to a robust production environment. Preserving and migrating this data to a production environment helps ensure the rapid adoption of Lotus Connections when it is deployed at the enterprise level.
Migration can be accomplished only if the users that participated in the pilot deployment are identical to the users in the LDAP that will be used by the production deployment. These early adopters will seed the Lotus Connections user community. After migration is complete, new users can be added.
Migration transfers data from a pilot to a production server, and also synchronizes member information from the pilot user flat file with the LDAP production environment. A user's e-mail address is the key value in synchronization. The e-mail address must be identical in both the pilot user information file and in the production LDAP system. If the e-mail addresses are not identical, user synchronization cannot succeed.
Steps to successful migration
Migration includes the following general steps:
- Production database creation: The backup of the pilot database and subsequent creation of a production database
- Application update: The installation of a production version of Lotus Connections and connection to the new production database
- Pilot-to-production data transfer: Migration of user data from the pilot database to the new database used by the production environment.
- LDAP synchronization: The updating of member IDs in the new database to match the LDAP that is used by the production deployment
- Cleanup and completion: Tasks that finalize the production installation
Migration and individual features
The complexity of migration depends on the number of features installed as part of the pilot deployment. If you have not installed a specific feature as part of the pilot deployment, you can ignore instructions related to migrating data related to that feature.
- Migrating a pilot deployment
The steps required to migrate a pilot deployment to a production deployment depend on the features installed with the pilot deployment.
Migrating to Lotus Connections 2.5