Migrating to IBM® Connections 6.0

Migrate an installation of HCL Connections™ 5.0 or 5.5 to Connections 6.0. For any version of Connections before version 5.0, you must migrate to version 5.0 before you migrate to version 6.0.

Before you begin

Note: If you are migrating from version 4.5, or you are migrating from either version 5.0 or 5.5 that was previously migrated from version 4.5, and you have FileNet implemented, during CPE upgrade, the CPE upgrade portion is supposed to change the setting in the FileNet security Directory Configuration from VMM to CONNECTIONS.
To check that the FileNet security Directory Configuration in version 6 has the correct setting, take the following steps:
  1. Log in to the Acce Console server:port/acce.
  2. Go to the IC Domain - Directory Configuration.
  3. Make sure that the FileNet security Directory Configuration is set to CONNECTIONS.
  4. Make sure that the Directory Server Provider Class is com.filenet.engine.security.ConnectionsProvider.
If you want to change the display name to "IBM Connections Directory Service," follow these steps:
  1. Log in to the Acce Console as a P8 domain administrator.
  2. Click the Directory Configuration tab, and click IBM Virtual Member Manager.
  3. Click Display Name and select Display or Edit Value from the list.
  4. Change the value to IBM Connections Directory Service.
  5. Click the domain tab, click ICDomain, and click Save.

Before you begin the migration, also address the following items:

  • Ensure that your environment meets the hardware and software requirements for IBM® Connections 6.0 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 Connections 6.0 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 Connections 6.0, using the same hardware you used for the previous release. You must uninstall Connections 5.0 or 5.5 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 5.0 GA, 5.0 (with CRs), 5.5 GA and 5.5 (with CRs) can be migrated directly to Connections 6.0.

Procedure

Complete all steps that apply to your deployment.
  1. Advise users about any possible outages. For more information, see Informing 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 the following topics: Backing up IBM Connections, Saving your customizations, and Backing up Cognos Business Intelligence reports.
  3. Stop Connections 5.0 or 5.5.
  4. Export Connections artifacts. For more information, see Exporting application artifacts from IBM® Connections 5.0 or 5.5.
  5. Migrate Connections 5.0 or 5.5 data. For more information, see Migrating data from IBM® Connections 5.0 or 5.5 databases to 6.0.
  6. Optional: Uninstall Connections 5.0 or 5.5. This action is recommended if you are installing 6.0 in place. This step is not necessary if you install version 6.0 on new hardware.
    Note: Uninstalling Connections 5.0 or 5.5 also removes your FileNet® deployment. Save the FNGCD and FNOS databases of IBM® Connections Content Manager; you connect to these older databases during the migration.
  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 6.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 6.0. For more information, see Installing IBM® Connections 6.0 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 6.0. When you are prompted to enter the database information, connect to the FNGCD and FNOS databases of Connections 5.0 or 5.5.
  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 5.0 or 5.5 to the EXTRACTED_FILE_STORE location on the 6.0 system as part of the content store migration.

  12. Import IBM® Connections 5.0 or 5.5 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: