Prerequisites

Prerequisites to migrate your data from IGI to either Software Stack or Container using the IGI Migration Tool.

Overview

Refer the "Planning " page before proceeding with the next steps. Plan out the entities to be migrated and set the prerequisites for execution of IGI Migration Tool.

Folder structure

Below is the typical folder structure where command line utilities for IGI Migration Tool will reside on an IVIG Software Stack setup.

<Liberty_Home>/usr/servers/defaultServer/bin/IGIMigration

The IGIMigration directory will contain below sub-directories.

  • config - This will contain multiple properties files which are required to configure the migration tooling utility.

  • bin - This will contain executable scripts to perform the migration.

  • logs - This will contain the logs related to execution of the migration utility.

  • jar - This will contain the binaries.

  • result - After the utility execution, the success and failure results will be uploaded here.

  • csv - If the csv file creation path is not specified explicitly in the config file, this directory stores all the extracted CSV files from ISVG-Gov system.

  • json - If the json file creation path is not specified explicitly in the config file, this directory stores all the json files. These json files contain data parsed from CSV file and converted into JSON format for further loading it into IVIG system.

Prerequisites

  1. Ensure the ISVG-Gov database is accessible from the IVIG setup from where the migration needs to be performed.

  2. Obtain the IGI DB credentials to connect to the IGI database.

  3. Plan the steps in the migration before executing the utility. These steps could include a combination of below operations, entities and configurations. Pick an operation along with one or more entities and configurations for each step of the migration. Refer Planning section for more details about each operation, entity and configuration.

Operations:

  1. Read

  2. Convert

  3. Load

Entities:

  1. Persons/Users

  2. User account mappings.

  3. Roles

  4. Applications

  5. Hierarchies

  6. Risks SA/SoDs

  7. Activities

  8. Mitigations

Configurations:

  1. User configurations

  2. Application configurations

  3. Account configurations

  4. OU configurations

  5. Role configurations

  6. Provisioning rules

  7. Campaign configurations

  8. Email notifications

  1. Ensure that the Java Runtime Environment is installed and accessible from the path where migration utility is executed.

  2. Update the following configuration files as per requirement.

    1. application.properties file

    2. igisql.properties file

    3. mapping.properties file