Upgrade - Connections 4.x to 5.0


Task Resource Dev QA Prod Notes
Verify system requirements. Architect Pend Pend Pend
Verify migration path Architect Pend Pend Pend
Review data migration strategy Architect Pend Pend Pend
Create new 4.x databases on separate system Admin Pend Pend Pend
Transfer data from source 4.x DBs to target 4.x DBs Admin Pend Pend Pend
Update new 4.x DBs to Connections v5.0 Admin Pend Pend Pend Upgrade Homepage DBs first
Rename cell, nodes, servers, cluster Admin Pend NA NA Portal only
Back up the current deployment Architect Pend Pend Pend Includes customized files
Migrate content stores Architect Pend Pend Pend
Install IBM WAS v8.5.5.1. Admin Pend Pend Pend
Create required Manager and AppServer profiles Admin Pend Pend Pend Cell profile
Install WAS fix Admin Pend Pend Pend
Set LDAP with federated repositories in WAS Admin Pend Pend Pend
Use TDI to populate Profile database TBD N/A N/A N/A Not required for migration
Create Cognos administrator account TBD Pend Pend Pend
Install DB client for Cognos TBD Pend Pend Pend
Install WAS for Cognos TBD Pend Pend Pend Use a new wizard to install after installation of Connections.
Create AppServer profile for Cognos TBD Pend Pend Pend
Apply fixes TBD Pend Pend Pend
Install Cognos BI and Transformer Server TBD Pend Pend Pend
Federate Cognos TBD Pend Pend Pend
Install Cognos fix packs Admin Pend Pend Pend
Install IHS, Plugin, and fixes Admin Pend Pend Pend
Install Connections 5.0 for migration Admin Pend Pend Pend
Apply CNX fixes Admin Pend Pend Pend
Configure IHS, and SSL Admin Pend Pend Pend
Export artifacts from 4.x TBD Pend Pend Pend
Import artifacts to 5.0. TBD Pend Pend Pend
Post-migration Admin Pend Pend Pend
CNX Forms Experience Builder Admin Pend Pend Pend
Migrate search index Admin Pend Pend Pend
String Customization Dev Pend Pend Pend
Media gallery Architect Pend Pend Pend
Polls and surveys Arch Pend Pend Pend
    User interface customizations TBD Pend Pend Pend Header, navigation, footer
Portal upgrade TBD Pend Pend Pend
Enable mobile device access in Portal TBD Pend Pend Pend
Integrate IBM eForms TBD Pend Pend Pend
Promote TBD Pend Pend Pend Dev --> QA --> Prod
Syndicate TBD Pend Pend Pend Dev --> QA --> Prod
Test TBD Pend Pend Pend
Review JVM heap TBD Pend Pend Pend
Configure Home page administrator Admin Pend Pend Pend
Configure File Downloads through the HTTP server Admin Pend Pend Pend
Grant access to Global Metrics and Community Metrics Admin Pend Pend Pend
Configure ConnectionsMetricsAdmin role on Cognos Admin Pend Pend Pend
Configure Cognos to use the HTTP Server and SSL Admin Pend Pend Pend
Validate Cognos TBD Pend Pend Pend
Configure the Job Scheduler Admin Pend Pend Pend
Configure Connections Content Manager for Libraries Admin Pend Pend Pend
    Generate synchronization reports TBD Pend Pend Pend
Generate configuration setting reports TBD Pend Pend Pend
Verify TBD Pend Pend Pend
Modify JDBC to point to production DB TBD Pend Pend Pend
Go-live TBD Pend Pend Pend


Scope

Dev Single-node cluster
QA Two-node cluster
Prod Two-node cluster


Migration path

Migrating Connections 4.0/4.0 CRx (Cumulative Release version) or Connections 4.5/4.5 CRx directly to Connections 5.0 is supported. For versions of Connections prior to v4.0, migrate to v4.0 before migrating to v5.0.

If we are deploying v5.0 on a different system from v4.x, you do not need to uninstall Connections 4.x.

If possible, set up a test environment, and simulate the migration process.

We can migrate the following directly to v5.0...

A side-by-side migration strategy minimizes the downtime, but costs more in terms of hardware resources. An in-place strategy minimizes hardware costs but causes more downtime.


IBM Connections 4.0 to 5.0 Migration Steps

  1. Check existing content stores - must be shared disk between nodes Need those mounted on new hosts

  2. Backup Existing Connections

    • DB
    • DMGR Profile
    • App Profiles
    • Local Data
    • Shared Data
    • profileRegistery

  3. Save Customizations

  4. Migration Media Gallery

  5. Migration Connections Content Manager
    1. Install new FileNet Deployment
    2. Restore FileNet Storage Area
    3. Migration Encryption Keys

  6. Migration Cognos BI
    1. Backup Customized Reports
    2. Export Customized Reports
    3. Create new Cognos Database
    4. Install Connections 5.0
    5. Install Cognos BI Server
    6. Configure BI Server
    7. Import customized Reports
    8. Restore customized Reports

  7. Export Application Artifacts
    1. Full Sync
    2. cd /opt/IBM/Connections/migration
    3. ./migration.sh lc-export

  8. Content Store Migration
    1. Copy Existing Content Stores to new host
    2. Rename profiles and statistics subdirectories after copying to reflect the node and cluster names on the target system.

  9. Migrate Data

    1. Set WAS Statement cache size no larger than 50.
    2. Use DB Wizard to create 4.0 databases on the target system
    3. Update target databases to same CR as source DB
    4. Run predbxferxx.sql for each application DB
    5. Transfer data to new DB using provided tool
    6. Run postdbxferxx.sql for each application DB
    7. Update DB sequence

  10. Installations

    1. Pre-Req
      1. WAS Fixes
      2. IIM Versions
      3. Prepare LDAP Directory
      4. Install WAS
      5. Setup Federated Repository
      6. Linux Libraries
        • compat-libstdc++-33.x86_64
        • libcanberra-gtk2.i686
        • PackageKit-gtk-module
        • gtk2.i686
        • compat-libstdc++-33.i686
        • compat-libstdc++-296
        • compat-libstdc++
        • libXtst.i686
        • libpam.so.0
      7. Set File Descriptor Limit

    2. Install DMGR
    3. Create Managed and Default profiles (Cell profile)
    4. Run addNode.sh to federate default profile to dmgr.
    5. Use IIM to install Connections
    6. Import application artifacts
        ./migration.sh lc-import
    7. CleanUp duplicate login exceptions
        execfile('communitiesAdmin.py')
    8. For each file-based repository user
        CommunitiesMemberService.syncMemberExtIdByLogin("wasadmin")

  11. Post Migration
    1. Reapply customizations
    2. Reapply proxy configs
    3. Migrate Content Search Indexes
    4. Sync member db tables
    5. Reinstall connectors
    6. Server Whitelist
    7. Root URL updates
    8. Update HTTP Server
    9. Sync Files shared with communities
    10. Profile Type and Policy Changes