Introduction
New customers install DirX Audit according to the DirX Audit Installation Guide and work with the product. Existing customers must migrate their environment.
The DirX Audit supports upgrade and update installations. An Upgrade installation is used to migrate an existing product installation to a newer version of DirX Audit. An Update installation is used to migrate an existing product installation to a newer patch version of DirX Audit.
The upgrade process includes updating product components, database schema (if applicable), and configuration settings while retaining existing data and system configuration.
The update process doesn’t delete some runtime data such as logs and message broker database.
Migration from DirX Audit 7.1 SP2, 7.2, 9.0 and 9.1
Migration from DirX Audit 7.1 SP2, 7.2, 9.0, and 9.1 requires preparation steps, an upgrade or update installation including the initial configuration, and then the migration steps described in the next chapters.
The migration procedure consists of updates to the audit messages database (Data DB), the history entries database (History DB), and the configuration database (Config DB).
Features to be Migrated
This section provides an overview of the features to be migrated and explains the underlying concepts.
Issues Relevant for Upgrade from 7.1 SP2 to 7.2
This section comprises all issues relevant for version 7.1 SP2 only.
Audit Messages Database Update
The database behavior when DAT_AUDITEVENTS records are deleted has been modified for both SQL Server and Oracle Database.
History Entries Database Update
Since DirX Audit 7.2, user-to-privilege assignments are synchronized the same way as other entry types. Consequently, the HST_ASSIGNMENTS_IN_TIME table has been removed from the database schema and all its original data will be migrated during the manual migration process. In addition, the HST_ROLEPARAMS_IN_TIME table has been modified to reflect these changes.
The FCT_HST_IMPORTED_MEMBERSHIPS view has been replaced with the table of the same name to improve performance.
The FCT_RSK_COMPOUND_USERS view and RSK_COMPOUND_STATISTICS, RSK_COMPOUND_SCORES, RSK_STATISTICS, RSK_SCORES, RSK_COMPOUND_FACTOR_WEIGHTS, RSK_COMPOUND_FACTORS, RSK_FACTORS, and RSK_LEVELS tables have been removed as DirX Audit risks have been deprecated and only DirX Identity risk data is available.
The HST_ENTRIES table has been modified, the DIRX_ENTRY_UUID column is considered mandatory and unique.
The HST_LDAP_ATTRS table has been extended with a new column TYPE_NAME.
A new HDB_ASSIGNMENTS view has been added to provide data on assignments.
The HDB_ENTRY_OBJECTS view has been removed.
The HDB_ENTRY_ATTRIBUTES, HDB_USER_ROLES, HDB_USER_PERMISSIONS, HDB_USER_GROUPS, HDB_USER_ACCOUNTS, HDB_ROLE_ROLES, HDB_ROLE_PERMISSIONS, and HDB_PERMISSION_GROUPS views have been modified to improve performance.
The HDB_USER_PRIVILEGES view has been added.
Other minor improvements and fixes were also made.
Issues Relevant for Upgrade from 7.2 to 9.0
This section comprises all issues relevant for version 7.2 only.
Issues Relevant for Upgrade from 9.0 to 9.1
Configuration Database Update
The following configuration database tables are now deprecated and are not used to store config entries anymore: CFG_CONFIGENTRY_COMPONENT, CFG_CONFIGENTRY_TREEELEMENT, CFG_COMPONENT, CFG_CONFIGENTRY, CFG_DASHBOARD, CFG_CONFIGURATION, CFG_PARAM, CFG_TREE_ELEMENT.
These tables can be deleted after the contained data has been migrated to the new configuration database tables. For details see manual migration steps in the “Migrating DirX Audit” section of this document.
Issues Relevant for Upgrade from 9.1 to 9.1.1
This section comprises all issues relevant for version 9.1 only.
History Entries Database Update
The HDB_ENTRY_ATTRIBUTES view has been updated.
Fixed an issue in history purge procedures.