Manual Migration

This chapter assumes that the DirX Audit 7.2 upgrade installation has successfully started. If you are upgrading from DirX Audit 7.1 or 7.1 SP1 or 7.1 SP2, the Installation Wizard displays the dialog “Manual Migration Steps” with information that you are upgrading from an older version and must execute the manual steps described in this chapter.

At this stage, perform all the relevant steps described in this chapter to update your environment to the new DirX Audit version.

When you are migrating from an older DirX Audit version, you must proceed step by step from the oldest version as described in the following sections. We also suggest consulting the DirX Audit Migration Guide for each respective version (available at the Atos support portal) for a more detailed description of changes and updates, including more items than just the list of migration scripts. When migrating from DirX Audit 7.1, you can continue with the section “Migrating Databases from DirX Audit 7.1 to 7.1 SP1”. When migrating from DirX Audit 7.1 SP1, you can continue with the section “Migrating Databases from DirX Audit 7.1 SP1 to 7.1 SP2”. When migrating from DirX Audit 7.1 SP2, you can continue with the section “Migrating Databases from DirX Audit 7.1 SP2 to 7. 2”.

Migrating Databases from DirX Audit 7.1 to 7.1 SP1

Migrating the databases to DirX Audit 7.1 SP1 consists of migrating the audit messages database schema (Data DB) and the history entries database schema (History DB) for each tenant.

DirX Audit 7.1 SP1 can function with the same audit messages and history entries databases from the previous version, but some database objects must be altered.

  • Migrate the audit messages database schema - run the following SQL scripts in your audit messages database (Data DB) server console.

    For SQL Server:
    install_media/Additions/Scripts/MSSQL/migrate_data_71_71SP1.sql

    For Oracle Database:
    No action is required.

  • Migrate the history entries database schema - run the following SQL scripts in your history entries database (History DB) server console.

    For SQL Server:
    install_media/Additions/Scripts/MSSQL/migrate_history_71_71SP1.sql

    For Oracle Database:
    install_media/Additions/Scripts/Oracle/migrate_history_71_71SP1.sql

Continue with the steps described in the section “Migrating Databases from DirX Audit 7.1 SP1 to 7.1 SP2”.

Migrating Databases from DirX Audit 7.1 SP1 to 7.1 SP2

Migrating the databases to DirX Audit 7.1 SP2 consists of migrating only the history entries database schema (History DB) for each tenant.

DirX Audit 7.1 SP2 can function with the history entries database from the previous version, but some database objects must be altered.

  • Migrate the history entries database schema - run the following SQL scripts in your history entries database (History DB) server console.

    For SQL Server:
    install_media/Additions/Scripts/MSSQL/migrate_history_71SP1_71SP2.sql

    For Oracle Database:
    install_media/Additions/Scripts/Oracle/migrate_history_71SP1_71SP2.sql

Continue with the steps described in the section “Migrating Databases from DirX Audit 7.1 SP2 to 7.2”.

Migrating Databases from DirX Audit 7.1 SP2 to 7.2

Migrating the databases to DirX Audit 7.2 consists of migrating the audit messages database schema (Data DB) and the history entries database schema (History DB) for each tenant.

DirX Audit 7.2 can function with the same audit messages and history entries databases from the previous version, but some database objects must be altered. The migration must be done in several phases.

  • Migrate the audit messages database schema - run the following SQL scripts in your audit messages database (Data DB) server console.

    For SQL Server:
    install_media/Additions/Scripts/MSSQL/migrate_data_71SP2_72.sql

    For Oracle Database:
    install_media/Additions/Scripts/Oracle/migrate_data_71SP2_72.sql

  • Begin the migration of the history entries database schema - run the following SQL scripts in your history entries database (History DB) server console.

    For SQL Server:
    install_media/Additions/Scripts/MSSQL/migrate_history_71SP2_72_part1.sql

    For Oracle Database:
    install_media/Additions/Scripts/Oracle/migrate_history_71SP2_72_part1.sql

  • Clean up the DirX Identity domain and optionally the history entries database – remove duplicate LDAP entries with the dxthistdbtool command line tool and its ldapremdup command by following the steps described in the section “Remove Duplicate LDAP Entries” in the DirX Audit User Interface Guide. You may want to synchronize the changes made in the DirX Identity domain to the DirX Audit History Database. In this case, the following extension to the existing SQL Server JDBC connection string in the tenant configuration (install_path/conf/tenants/tenantID/configuration.cfg) could be required if you do not use a secure connection to your SQL database: encrypt=false.

    Example:

    dxthistdbtool ldapremdup
     -ldapconfig ldap.properties
     -tenantid 6bc24196-327d-441c-8d66-3633ee6b887b
     -synctohistdb

  • Clean up the history entries database – ensure there are unique history entries in the DirX Audit History Database with unique and non-missing dirxEntryUUID values with the dxthistdbtool command line tool and its makeunique command by following the steps described in the section “Make History Entries Unique” in the DirX Audit User Interface Guide.

    Example:

    dxthistdbtool makeunique
     -ldapconfig ldap.properties
     -tenantid 6bc24196-327d-441c-8d66-3633ee6b887b
     -csvfile duplicates.csv

  • Finish the migration of the history entries database schema - run the following SQL scripts in your history entries database (History DB) server console.

    For SQL Server:
    install_media/Additions/Scripts/MSSQL/migrate_history_71SP2_72_part2.sql

    For Oracle Database:
    install_media/Additions/Scripts/Oracle/migrate_history_71SP2_72_part2.sql

Next, continue with the steps described in the next sections.

Checking Apache Tomcat

To run DirX Audit Manager, you must install Apache Tomcat, which serves as the DirX Audit Manager’s container, if it is not already installed. For the supported version numbers, see the DirX Audit Release Notes. Alternatively, you can stop the running Apache Tomcat service and then remove the folder tomcat_install_path/work/Catalina/localhost/AuditManager.

Clearing Cached Internet Browser Data

We recommend that you remove the cached web content data, cookies and site data from your internet browser. This step is mandatory for Firefox, where you can find it in browser Tools → Settings → Privacy & Security → Clear Data.

Performing Initial Configuration

Now you can start the initial Core and Tenant configuration for each of your tenants by clicking Next in the Installation Wizard.

DirX Identity Synchronization Workflows are discontinued in DirX Audit 7.2 and replaced with History Synchronization based on LDAP. The existing workflows are migrated during the initial tenant configuration. For more details, see “Discontinued DirX Identity Synchronization Workflows Migration Connectivity Configuration” in the DirX Audit Installation Guide.

During DirX Audit configuration, an automatic procedure runs and performs migration steps. However, you must also perform some of the migration steps later as separate tasks, as described in the next sections.

For more information about the configuration process, see the section “Configuring DirX Audit” in the DirX Audit Installation Guide.

When the Configuration Wizard completes, finish the installation: Click Done to quit the installer.

Starting Services

At this point, you have DirX Audit 7.2 installed and at least one tenant configured on your system. Now start the DirX Audit services, if not already started, in this order:

  1. DirX Audit Message Broker

  2. DirX Audit Server tenant_display_name (a separate instance of DirX Audit Server is created for every tenant)

  3. The Apache Tomcat service where you deployed DirX Audit Manager

Update Scheduled Report Jobs

Remove all Generate dashboard chart reports in your existing/scheduled report sets referring to the following legacy Dashboard components:

  • Risk users based on compound factor by month and risk level

  • Risk users based on simple factor by month and risk level

  • DirX Identity total history certification campaign entries by month and lifecycle state

This step must be performed by all users that have these scheduled report jobs.

Update all report configurations for modified report templates. Several report templates have been updated. If they are included in a scheduled report job, this may require a manual configuration review – this means opening each individual report in a report set and resaving its configuration.

Update Set of Dashboard Components

Remove the following private and public legacy Dashboard components:

  • Risk users based on compound factor by month and risk level

  • Risk users based on simple factor by month and risk level

  • DirX Identity total history certification campaign entries by month and lifecycle state

and remove all custom components based on the same templates or based on these fact tables:

  • FCT_RSK_COMPOUND_USERS

  • FCT_RSK_USERS

  • FCT_HST_CERTCAMPAIGNS_LIFECYCLE

in the Manage Components list. These components cannot be used anymore. This step must be performed by all users that have these Dashboard components in their lists.