Preparing the Migration

The following step is necessary to prepare the migration:

  • Back up the DirX Audit configuration database (Config DB), audit messages database (Data DB) and history entries database (History DB) to be able to reset to the starting point if something goes wrong.

Depending on the features you used, you need to perform the steps described in the next sections.

Archive Error Handling Data

Archive the DirX Audit Server error handling folder for each of your tenants and keep it empty before starting a new version of the DirX Audit product.

Stop All Message Broker Connections

Apache ActiveMQ will be upgraded during the DirX Audit 9.0 installation, so users should make sure that all Message Broker connections have been stopped and that there are no pending messages waiting in individual queues.

Archive Custom Data and Stop Services

We strongly recommend backing up all configuration- or customer-specific files, especially for the DirX Audit Server configuration, added to the installation folder manually before performing the upgrade. The DirX Audit Server will be upgraded and its structure, configuration files and libraries will change completely.

Also backup fact and dimension configuration files, which are all contained in the folder install_path/conf/tenants/tenantID/fact-configuration when tenant-specific customization is defined or in the folder install_path/conf/fact-configuration where the default definition is available:

  • confFactTables.xml – fact tables configuration file.

  • confFacts.xml – facts configuration file.

  • confDimensions.xml – dimensions configuration file.

All existing fact population configuration files, including customizations, will be removed during the installation.

Stop the DirX Audit services manually, including the Apache Tomcat service if it was used to start the DirX Audit Manager Classic.

Prepare the Configuration Database

You can use the same configuration database (Config DB) as for DirX Audit 7.1, DirX Audit 7.1 SP1, DirX Audit 7.1 SP2 and DirX Audit 7.2. The configuration database schema will be updated during the migration process.

Prepare the Audit Messages Database

You can use the same audit messages database (Data DB) as for DirX Audit 7.1, DirX Audit 7.1 SP1, DirX Audit 7.1 SP2 and DirX Audit 7.2. The audit messages database schema will be updated during the migration process.

Prepare the History Entries Database

You can use the same history entries database (History DB) as for DirX Audit 7.1, DirX Audit 7.1 SP1, DirX Audit 7.1 SP2 and DirX Audit 7.2. The history entries database schema will be updated during the migration process.

Install the Java VM

The Java Virtual Machine (Java VM, JVM) is required for the DirX Audit installation. The installation will not start without Java VM installed; instead, it displays an error message indicating that a valid Java VM is missing.

When the installation runs, it prompts you to identify the folder in which the Java VM is installed. Make sure you have an appropriate Java VM installed.

You must also check whether the JAVA_HOME and PATH environment variables are set correctly for your operating system. See the DirX Audit Release Notes for supported versions.

If you store your keys in the cacerts file, make a backup copy before starting the installation and have it available with the Java VM used for DirX Audit.