How to Upgrade to DirX Identity 9.0
Purpose
This guide walks you through the complete process of upgrading an existing DirX Identity installation to version 9.0.
| Each step described in this section is mandatory. Skipping or altering steps may result in an incomplete upgrade, configuration errors, or malfunctioning services after installation. Please follow the procedure carefully and in the order presented to ensure a stable and fully functional system after the upgrade. |
Pre‑Upgrade Preparation
Before starting the upgrade, the environment must be brought into a defined and consistent state. This mainly involves stopping specific services to ensure that no files are locked and no background processes interfere with the installer.
Stop Required Services
Prior to launching the DirX Identity 9.0 installer, stop the following services in the exact order listed below:
-
Apache Tomcat
-
Java Server
-
C Server
-
Message Broker
|
Do not stop the DirX service. The DirX service is required during the upgrade. If it is stopped, the Configuration Wizard will fail and the installation cannot be completed successfully. |
Installation and Configuration Wizard
Start the DirX Identity 9.0 installer and proceed through the initial installation steps until the Configuration Wizard is launched.
| The following dialogs require special attention during an upgrade installation. |
Password Policies Dialog
When the Password Policies dialog appears:
-
Click Set all to default.
-
Click OK to continue.
| During an upgrade, this dialog does not apply changes to existing password policies. However, selecting the default values ensures consistency and avoids unnecessary validation issues during the wizard execution. |
Incorrect LDAP Bind Values Dialog
During the wizard, the dialog Incorrect LDAP Bind Values is displayed.
-
Click Correct Values….
-
Enter the following credentials if they are not already prefilled:
-
Username:
cn=admin,dxmC=DirXmetahub -
Password:
dirx (admin password)
-
-
Click Authenticate.
-
Click OK to confirm.
Post‑Installation File Synchronization
After the Configuration Wizard completes, several configuration files generated during the upgrade must be synchronized manually.
Locate .new Configuration Files
-
Open two File Explorer windows.
-
In the first window, navigate to the DirX Identity installation directory:
<DXI_INSTALL_PATH> -
Use the search field and search for:
*.new
This will list all newly generated configuration files created during the upgrade process.
Replace Existing Configuration Files
For each file with the .new extension, perform the following steps:
-
In the second File Explorer window, navigate to the directory where the file is located (for example:
<DXI_INSTALL_PATH>\gui\bin for cdwizard.cfg.new). -
Open both files in a text editor (for example, Notepad++):
-
The file with the
.newextension (e.g. cdwizard.cfg.new) -
The file with the same name without the .new extension (e.g. cdwizard.cfg)
-
-
Copy the entire content of the
.newfile. -
Overwrite the complete content of the file without the
.newextension. -
Save the file without the
.newextension. -
Close both editor windows.
-
Delete the
.newfile.
Repeat this procedure for all .new files found.
Verification
Once all files have been processed:
-
Search again in
<DXI_INSTALL_PATH>for:*.new -
Verify that no files with the
.newextension remain.
If any .new files are left in place, DirX Identity will not operate correctly. Users may encounter GUI error popups indicating that required configuration files cannot be found.
|
Post‑Upgrade Compilation Step
Recompile Connected Directories
To finalize the upgrade, internal objects must be recompiled:
-
Open DirX Identity Manager.
-
Navigate to Connectivity.
-
Switch to the Expert View tab.
-
Expand the Connected Directories node by clicking the expand arrow next to it.
-
Right‑click Connected Directories.
-
Select Recompile All.
The Connected Directories node must be fully expanded (step 4) before
selecting Recompile All. If the node is not expanded first, DirX Identity Manager
may throw an IllegalStateException and the action appears to complete without
actually recompiling any mappings. This is a known issue in DirX Identity 9.0.1,
fixed in 9.0.2.
|
| If this step is skipped, Java log files will contain errors and Java‑based workflows will not function correctly. |