Migrating to IBM Connections 5.5

Migrate a production installation of IBM® Connections 4.5 or 5.0 to IBM Connections 5.5. For any version of IBM Connections before version 4.5, you must migrate to version 5.0 before you migrate to version 5.5.

Before you begin

  • Ensure that your environment meets the hardware and software requirements for IBM Connections 5.5 and any interim fixes or Cumulative Refreshes (CRs) you plan to install. For more information, see IBM Connections system requirements.
  • Decide on a migration strategy and if needed install more hardware.
    • A side-by-side data migration strategy minimizes the downtime of your production environment but costs more in terms of hardware resources because you keep your older data active during migration. You install IBM Connections 5.5 and its supporting products on new hardware for testing before you deploy the new release. This strategy is used by most enterprises.
    • An in-place data migration strategy minimizes costs because you do not need to deploy new hardware. However, it causes more downtime because you take the deployment offline to migrate to IBM Connections 5.5, using the same hardware you used for the previous release. You must uninstall IBM Connections 4.5 or 5.0 and if applicable, Cognos Business Intelligence, before you install the new release.
    • 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. This change causes the affected users to look like different users if stored in the Communities database. Therefore, the Communities app might generate MemberDuplicateLoginIdExceptions since it finds what appears to be two distinct users that share the same login. To avoid this problem:
      1. Run the following command from a wsadmin prompt: execfile('communitiesAdmin.py')
      2. For each file-based repository user, run: CommunitiesMemberService.syncMemberExtIdByLogin("<login name>"), for example: 
        CommunitiesMemberService.syncMemberExtIdByLogin("wasadmin")

About this task

If possible, set up a test environment and simulate the migration process. Correct the cause of any errors that occur and then migrate your production environment.
Note: IBM Connections 4.5 GA, 4.5 (with CRs), 5.0 GA and 5.0 (with CRs) can be migrated directly to IBM Connections™ 5.5.

Procedure

Complete all steps that apply to your deployment.
  1. Advise users about any possible outages. For more information, see Informing IBM Connections users of a migration or update.
  2. Back up your current deployment, including databases, FileNet® software, and customized files and settings. For more information, see Backing up IBM Connections, Saving your customizations, and Backing up Cognos® Business Intelligence reports.
  3. Stop IBM Connections 4.5 or 5.0.
  4. Export IBM Connections 4.5 or 5.0 artifacts. For more information, see Exporting application artifacts from IBM Connections 4.5 or 5.0.
  5. Migrate your IBM Connections 4.5 or 5.0 data. For more information, see Migrating data from IBM Connections 4.5 or 5.0 databases to 5.5.
  6. Optional: Uninstall IBM Connections 4.5 or 5.0. This action is recommended if you are installing 5.5 in place. This step is not necessary if you install version 5.5 on new hardware.
    Note: Uninstalling IBM Connections 4.5 or 5.0 also removes your FileNet deployment. Save the FNGCD and FNOS databases of IBM Connections Content Manager; you connect to these older databases during the IBM Connections 5.5.
  7. Optional: Uninstalling Cognos BI. This action is recommended if you are installing Cognos BI in place. This action is not necessary if you are installing Connections 5.0 Cognos BI on new hardware.
  8. Upgrade IBM WebSphere® Application Server to the latest supported version that is needed for the latest Cumulative Refresh or interim fixes. For more information, go to the Installing maintenance packages, interim fixes, fix packs, and refresh packs in the WebSphere Application Server information center.
  9. Complete the pre-installation tasks that are relevant to migration. For more information, see Pre-installation tasks.

    Some of the Pre-installation tasks describe how to create databases or populate the Profiles database. You do not need to complete those particular tasks because the migration process automatically completes them.

  10. Install IBM Connections 5.5. For more information, see Installing IBM Connections 5.5 for migration.
    Note: To migrate Connections Content Manager, select the application during installation and select New deployment, even though you are migrating. This selection migrates the integrated version of FileNet to IBM Connections 5.5. When you are prompted to enter the database information, connect to the FNGCD and FNOS databases of IBM Connections Content Manager 4.5 or 5.0.
  11. Migrate your content stores. For more information, see Content store migration.

    Reuse the extracted file content that is stored at the location pointed to by the EXTRACTED_FILE_STORE WebSphere variable. You can achieve this step by copying the contents of EXTRACTED_FILE_STORE location on the 4.5 or 5.0 system to the EXTRACTED_FILE_STORE location on the 5.5 system as part of the content store migration.

  12. Import IBM Connections 4.5 or 5.0 artifacts. For more information, see Importing application artifacts to IBM Connections 5.5.

What to do next

Perform any of the following applicable tasks as needed; in particular take note of the Post-migration tasks: