Upgrading from ISVG IM Software to IVIG Software

Edit online

This section describes the steps for upgrading from ISVG IM Software Stack (WAS) to IVIG Software Stack (Liberty).

Overview

This topic describes the steps to upgrade from your existing ISVG IM Software Stack setup to IVIG Software Stack Liberty version 11.0.0.

Before you begin

Note the following nomenclature:
  • Source System: Existing ISVG IM -Software Stack setup
  • Target System: IVIG - Software Stack setup running on IBM WebSphere Liberty

While upgrading to IVIG Container, from IM SS or from IM VA, the first container deployment has to be done (without Enterprise/Complaince key) as Lifecycle Edition

Once the upgrade from SS/VA is completed successfully, then enable the Enterprise/Complaince features on the Container setup by using the setupAnalytics script.

Procedure

  1. Take a backup of the master key for the keystore of your ISVG IM -Software Stack setup (Source System).
  2. Take a backup of the following properties files for your ISVG IM -Software Stack setup:
    • enRole.properties
    • enRoleLDAPConnection.properties
    • enRoleDatabase.properties
    • encryptionKey.properties
    • itimKeystore.jceks
  3. On the Target System, run configure, and use the exactly the same values for LDAP and database as used on the Source System. In the case of IM/MQ hostnames, use the details for the Target System.
  4. Run install --module createKeystore
  5. Run migrateKeystore.sh and point to the relevant files that you had copied in step 2.
  6. Copy the enRole*.properties files into the config/data directory
  7. Run install --module imConfig

    This command updates the files with the required values.

  8. Run ldapUpgrade.sh
  9. Run dbUpgrade.sh
  10. Run upgradeRoleHierarchy.sh
  11. Start the IVIG Server.

Enable Identity Analytics

After the upgrade process is complete, perform the following steps to enable Identity Analytics.

  1. Ensure StorageClass is NFS
  2. Post-upgrade, verify that clusterURL is updated correctly in values.yaml. If the clusterURL is not updated correctly: Run the command:

    kubectl cluster-info

    If the returned URL contains 127.0.0.1, update the clusterURL setting in values.yaml with the real IP of the server.

  3. Edit values.yaml for Storage Mode

    Set storage.mode to:ReadWriteMany: If you have more than 1 node in your cluster.ReadWriteOnce: If you only have 1 node in your cluster.

  4. Ensure you have a valid Enterprise or Compliance key to proceed. Execute the setupAnalytics in Starter/bin/sys/ with your key:

    setupAnalytics.sh <ENTERPRISE_OR_COMPLIANCE_KEY>