Importing application artifacts to IBM Connections 5.5

Import application artifacts, including configuration data and properties files, into your new deployment.

Before you begin

Ensure that you completed the steps in Exporting application artifacts from IBM® Connections 4.5 or 5.0.

About this task

To import application data into your IBM Connections 5.5 deployment, complete the following steps:


  1. Start the Deployment Manager in your IBM Connections 5.5 deployment.
  2. Set the WAS_HOME environment variable. For more information, see Setting the WAS_HOME environment variable before updating.
  3. Copy the /work directory that you backed up from your 4.5 or 5.0 deployment to the connections_root directory in your 5.5 deployment.
    Note: Be sure not overwrite the 5.5 migration directory with the 4.5 or 5.0 migration directory. Copy the 4.5 or 5.0 migration/work directory into the existing migration directory on the 5.5 system only.
  4. Import your 4.5 or 5.0 data. Open a command line, change to the migration directory in the connections_root in your 5.5 deployment, and run the following command:
    • AIX or Linux:
      ./ lc-import -DDMUserid=dm_admin -DDMPassword=dm_password
    • Windows:
      migration.bat lc-import -DDMUserid=dm_admin -DDMPassword=dm_password
    • Where dm_admin is the administrative user ID for WebSphere® Application Server Deployment Manager and dm_password is the password.

    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:


    For example:
    • AIX or Linux:


    • Windows:

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

    • Windows Server 2008:


  5. If your deployment uses multiple nodes, synchronize the nodes.

What to do next

Complete the steps in Post-migration tasks.

If the migration fails, restore the Deployment Manager profile and complete the steps in this task again. If you customized your 4.5 or 5.0 environment, reapply your customizations to the relevant XML files.

For more information, see the Rolling back a migration topic.

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 change. This change causes these users to look like different users if they are stored in the Communities database. Therefore, communities might generate MemberDuplicateLoginIdExceptions because it finds two distinct users who share one login ID. To avoid this problem:
  1. Run the following command from a wsadmin prompt: execfile('')
  2. For each file-based repository user, run: CommunitiesMemberService.syncMemberExtIdByLogin("<login name>"), for example: