Home

 

Migrating a stand-alone deployment

Migrate your Lotus Connections 2.0.1 stand-alone deployment to release 2.5.

1. Back up your Lotus Connections 2.0.1 deployment. For more information, see the Backing up Lotus Connections topic.

2. Update your Lotus Connections 2.0.1 databases to release 2.5. The method you choose to update databases depends on your migration strategy. For more information, see the Updating databases topic. That topic also instructs you to install databases for new features such as Files and Wikis.

3. Advise users about any possible outages. For more information, see the Preparing Lotus Connections for maintenance topic.

Notes

• You must migrate to Lotus Connections release 2.5 from release 2.0.1. If you have an earlier release than 2.0.1, migrate that release to 2.0.1 before migrating to release 2.5. For more information, see the Migration strategies topic.

• If your 2.0.1 stand-alone deployment installed features on different WebSphere Application Server profiles, the 2.5 migration tool will automatically migrate the features correctly to your new 2.5 stand-alone or network deployment.

To migrate your Lotus Connections 2.0.1 stand-alone deployment to release 2.5...

1. Copy the migration from the Lotus Connections 2.5 installation media to the Lotus Connections 2.0.1 installation directory: LC_ROOT. Ensure that you copy the migration to the same level as the ConfigEngine

2. Export your 2.0.1 data. Open a command prompt, change to the migration and run the following command:

   The migration process can take a long time to complete, depending on the number and size of files in your content store directories. If the directories contain more than 1 GB of data, you should use the

   -DhandleData=false

   parameter to bypass the export. You then need to re-use the 2.0.1 content store directories for Lotus Connections 2.5; when you install 2.5 and you are prompted to select content store directories, specify the 2.0.1 directories.

   • AIX or Linux:

     ./migration.sh lc-export

   • Windows:

     migration.bat lc-export

   Notes

   • The lc-export command exports the following data:

     • Content in the data directories for each feature

     • Configuration files in the LotusConnections-config You can find this in a the following location:

       • Stand-alone deployment: profile_root/config/cells/cell_name/LotusConnections-config

       • Network deployment: DM_profile_root/config/cells/<DM_cell_name>/LotusConnections-config

     • Properties files in the LC_ROOT

   • The migration tool collects data from all the features even when they are in different WebSphere Application Server profiles. The location of each feature is recorded in the config engine in the LC_ROOT After extracting the 2.0.1 data, the tool uses the same method to determine where the 2.5 features are located and imports the data accordingly.

   • The exported data is stored in the migration Check the log file to validate the export. The log is stored in the system user's home directory, and uses the following naming format:

     lc-migration-yyyyMMdd_HHmm_ss.log For example:

     • AIX or Linux:

       /root/lc-migration-20090925_1534_26.log

     • Windows:

       C:\Documents and Settings\Administrator\lc-migration-20090925_1534_26.log

3. Back up the migration to a location outside your 2.0.1 deployment.

4. Uninstall Lotus Connections 2.0.1. For more information, see the Uninstalling Lotus Connections topic.

   Notes

   • The release 2.5 installation wizard does not automatically uninstall release 2.0.1.

   • You can keep your 2.0.1 deployment if you are installing release 2.5 on a separate system.

5. Update WebSphere Application Server to release 6.1.0.23. Go to the Fix Central Web site to download the required fix packs and update installer. Ensure that you download and install all of the applicable downloads from Fix Central, including the fix packs for WebSphere Application Server, Plug-ins, IBM HTTP Server, and Java™ SDK. Note that the Java SDK must be applied to the WebSphere Application Server, Plug-ins, and IBM HTTP Server components. For more information, see the Lotus Connections system requirements topic.

6. Install Lotus Connections 2.5, choosing the Stand-alone or Advanced Stand-alone option. For more information, see the Installing Lotus Connections topic.

7. Rename the LC_ROOT. /migration in your 2.5 deployment and then copy the migration that you backed up from your 2.0.1 deployment to the LC_ROOT. in your 2.5 deployment.

8. Import your 2.0.1 data. Open a command prompt, change to the migration in Lotus Connections 2.5, and run the following command:

   If you used the

   -DhandleData=false

   parameter during the data export, use that parameter when you run the import command.

   • AIX or Linux:

     ./migration.sh lc-import

   • Windows:

     migration.bat lc-import

   Notes

   • Check the log file to validate the import. The log file is stored in the system user's home directory, and uses the following naming format:

     lc-migration-yyyyMMdd_HHmm_ss.log For example:

     • AIX or Linux:

       /root/lc-migration-20090925_1534_26.log

     • Windows:

       C:\Documents and Settings\Administrator\lc-migration-20090925_1534_26.log

   • The imported data is stored in the LC_ROOT/Data directory.

Compete the steps in the Post-migration tasks topic.

If the migration failed, restore your Lotus Connections 2.0.1 environment. For more information, see the Rolling back a migration or update topic.

Migrating Lotus Connections features

Migration strategies

Updating databases

Install Lotus Connections

 

Related tasks

Prepare Lotus Connections for maintenance

Backing up Lotus Connections

Post-migration tasks

Uninstall Lotus Connections

 

Related reference

Lotus Connections detailed system requirements

---

+

Search Tips   |   Advanced Search