Import application artifacts to Connections 5.0

Overview

After exporting application artifacts from 4.x, we import these artifacts into v5.0.

Artifacts consist of configuration data and properties files.

Import application data into the Connections 5.0 deployment

1. Start the dmgr in the Connections 5.0 deployment.

2. Copy the migration directory backed up from the 4.5 deployment to the connections_root directory in the 5.0 deployment.
   scp -r /opt/IBM/Connections/migration/work user@newsystem:/opt/IBM/Connections/migration

   Do not overwrite the 5.0 migration directory with the 4.5 migration directory, we only copy over the /work subdirectory..

3. From the 5.0 host, import the 4.5 data...

   cd $DMGR_PROFILE/bin
   ./manageprofiles.sh -setDefaultName -profileName myDmgrProfile
   INSTCONFSUCCESS: Success: The default profile has been set.
   $ ./manageprofiles.sh -getDefaultName
   MyDmgrProfile
   cd /path/to/4.5/migration/work
   ./migration.sh lc-import -DDMUserid=wasadmin -DDMPassword=password
   • After completion, review log...

     HOME/lc-migration-yyyyMMdd_HHmm_ss.log

     For example:

     /root/lc-migration-20110215_1534_26.log

   • Synchronize nodes

Re-run lc-import

Export log...

IC_HOME/migration/work/migrate.latest.log

Search for ERROR or Exception in the log.

Restore configuration file from IC_HOME/migration/work/backup

1. Restore WAS Deployment Manager profile
2. Delete "import" and "backup" dir under IC_HOME/migration/work
3. Rerun lc-import

What to do next

Complete the steps in Post-migration tasks.

If the migration fails, restore the dmgr profile and complete the steps in this task again. If we customized your 4.5 environment, reapply the customizations to the relevant XML files. See Roll back a migration.

A file-based repository is commonly used for administrative user accounts. When the data is moved from one WebSphere deployment to another, the unique IDs for the file-based repository users effectively change, causing these users to look like different users are stored in the Communities database. As such, Communities might generate MemberDuplicateLoginIdExceptions since it has apparently found two distinct users sharing the same login id. To avoid this problem:

1. Run from a wsadmin prompt: execfile('communitiesAdmin.py')

2. For each file-based repository user, run sync. For example...
   CommunitiesMemberService.syncMemberExtIdByLogin("wasadmin")

Parent topic:
Upgrade Connections v4.x to Connections v5.0

Related:
Install the Connections Connector for Lotus Quickr
Post-migration tasks
Export application artifacts from IBM Connections 4.0 and 4.5
Roll back a migration