10.7 Migrating Identity Reporting

1. Upgrade the Data Collection Services and Managed Services Gateway driver packages. For more information, see Upgrading Installed Packages of the NetIQ Designer for Identity Manager Administration Guide.

   NOTE:While upgrading the packages, ensure that you specify the details of the new Identity Reporting server.

2. Deploy the drivers. For more information, see Deploying the Drivers for Identity Reporting.

3. (Conditional) If you are migrating from 4.5.x and desire to migrate the EAS data, perform the steps from Migrating Your Existing Data to a New Database.

1. Open the project in Designer and run the Project Checker on the migrated objects.

   For more information, see Validating Provisioning Objects in the NetIQ Identity Manager - Administrator’s Guide to Designing the Identity Applications. If validation errors exist for the configuration, you are informed of the errors. These errors must be corrected before you can deploy the driver.

2. In the Outline view, right-click the Data Collection Services driver.

3. Select Deploy.

4. Repeat this process for each Data Collection Services driver in the driver set. Once the Data Collection Service driver is deployed, repeat this process for Managed Service Gateway driver.

Prepare the New PostgreSQL Database

1. Stop EAS to ensure that none of the events are sent to the EAS server.

2. Using iManager, stop the DCS driver:

   1. Log in to iManager.

   2. Stop the DCS driver.

   3. Edit the driver properties to change the startup option to Manual.

      This step ensures that the driver does not start automatically.

3. Run the following SQL commands to create the required roles, table space, and database using PGAdmin.

   This step ensures there are no failures during migration.

   1. Run the following commands to create the required roles:

      CREATE ROLE esec_app
        NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
       
      CREATE ROLE esec_user
        NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
       
      CREATE ROLE admin LOGIN
        ENCRYPTED PASSWORD '<specify the password for admin>'
        NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
      GRANT esec_user TO admin;
       
      CREATE ROLE appuser LOGIN
        ENCRYPTED PASSWORD '<specify the password for appuser>'
        NOSUPERUSER INHERIT NOCREATEDB CREATEROLE;
      GRANT esec_app TO appuser;
       
      CREATE ROLE dbauser LOGIN
        ENCRYPTED PASSWORD '<specify the password for dbauser>'
        SUPERUSER INHERIT CREATEDB CREATEROLE; 
      
      CREATE ROLE idmrptsrv LOGIN
        ENCRYPTED PASSWORD '<specify the password for idmrptsrv>'
        NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
      GRANT esec_user TO idmrptsrv;
       
      CREATE ROLE idmrptuser LOGIN
        ENCRYPTED PASSWORD '<specify the password for idmrptuser>'
        NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
      
      CREATE ROLE rptuser LOGIN
        ENCRYPTED PASSWORD '<specify the password for rptuser>'
        NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
      GRANT esec_user TO rptuser; 

   2. (Conditional) Run the following command for creating table spaces:

       CREATE TABLESPACE sendata1
        OWNER dbauser
        LOCATION '<provide the location where table space has to be created>'; 

      For example,

      CREATE TABLESPACE sendata1
        OWNER dbauser
        LOCATION '</opt/netiq/idm/apps/postgres/data>';

   3. (Conditional) If you want to migrate the existing EAS data, NetIQ recommends that you run the following command to create a SIEM database:

      CREATE DATABASE "SIEM"
        WITH OWNER = dbauser
             ENCODING = 'UTF8'
             TABLESPACE = sendata1
             CONNECTION LIMIT = -1;

   4. Run the following command to create a Reporting database:

      CREATE DATABASE "idmrptdb"
        WITH OWNER = dbauser
             ENCODING = 'UTF8'
             CONNECTION LIMIT = -1;

1. Download the Identity_Manager_4.7_Linux.iso from the NetIQ Downloads website.

2. Mount the .iso.

3. From the /mnt/ directory, install Identity Reporting.

   ./install.sh

4. Configure Identity Reporting.

   ./configure.sh

5. Select Custom configuration and choose No for the following prompts:

   Do you want to configure PostgreSQL database on current server?

   Do you want to install a new driverset?

   NOTE:By default, Identity Reporting installation creates and deploys the drivers for Managed Services Gateway and Data Collection Services.

6. Navigate to the configuration update utility located at /opt/netiq/idm/apps/configupdate directory and ensure that the configuration settings are correct:

   ./configupdate.sh