Importing application data to IBM Connections 3.0.1Added by IBM | Edited by IBM on March 15, 2012 | Version 3 (Show original)
|As part of the migration process, import application artifacts, such as configuration data and content stores, into your new deployment.
As part of the migration process, import application artifacts, such as configuration data and content stores, into your new deployment.
About this task
To import application data into your new IBM
® Connections deployment, complete the following steps:
- Start the Deployment Manager in your IBM Connections 3.0.1 deployment.
- Rename the lotus_connections_root/migration directory on the Deployment Manager node in your 3.0.1 deployment, and then copy the migration directory that you backed up from your 2.5 deployment to the lotus_connections_root directory in your 3.0.1 deployment.
- Import your 2.5 data. Open a command prompt, change to the migration directory on the Deployment Manager node in your 3.0.1 deployment, 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:
- where <dm_admin> is the administrative user ID for WebSphere® Application Server Deployment Manager and <dm_password> is the user password.
- The imported data is stored in the lotus_connections_root/Data directory.
- 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:
- AIX or Linux:
C:\Documents and Settings\Administrator\lc-migration-20110215_1534_26.log
- Windows Server 2008:
- If your deployment uses multiple nodes, perform a full synchronization of all nodes.
What to do next
Compete the steps in the Post-migration tasks
If the migration failed, restore your Connections 2.5 environment. For more information, see the Rolling back a migration
Parent topic: Migrating to IBM Connections 3.0.1 from version 2.5
Rolling back a migration