Preparing the Migration

These steps are necessary to prepare the migration:

  • Backup all DirX Identity databases 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 chapters.

Preserving Files

If you changed default parameters in files, back up these files.Examples of these changes are:

  • idmsvc.ini - you increased, for example, memory requirements (IdS-J server)

  • dxi.cfg - you made customizations according to the user documentation

  • runserver.bat or runserver.sh - you increased, for example, memory requirements

  • dxmmsssvr.ini - you used different port parameters, passwords or a certdb file path

  • domain.xml - you set a different search timeout limit than the default

  • bindcredentials.xml - you set your own timeout limits

  • password.properties - you provided PIN values for encryption or signature (IdS-J server) or SSL keystore password.The file is written anew by the Configurator, which asks you to set your PIN values.

  • gen*Keystores.bat/sh - scripts to generate keys; check for changed parameters

  • set_Environment.bat/sh - scripts to generate certificates and keys; check for changed parameters

  • web.xml - you changed parameters like SSL or debug

  • cacerts - you set up certificates for SSL in this file in the Java JRE folder dxi_java_home/lib/security.When creating the cacerts backup, ensure that your backup is outside dxi_java_home.

Customized Web Center

Create a backup copy of the related folders.

Provisioning Web Services and Related Clients

Create a backup copy of the file install_path/provisioningServices/spmlv2/conf.xml.

Perform these steps when upgrading from a Version lower than V8.5:

  • Create a backup copy of the related folder install_path/provisioningServlet.

  • Stop Tomcat (if you deployed said services into Tomcat) or Java-based server (otherwise), respectively.

  • Remove the file ProvisioningService.xml from the folder tomcat/conf/Catalina/locahost or from install_path\ids-j-domain-Sn/tomcat/conf/Catalina/localhost, respectively, in order to undeploy the obsolete servlet instance.

Perform this step when upgrading from Version V8.5 or higher:

  • Create a backup copy of each deployment instance folder of the folder install_path/provisioningWebServices, that is each sub-folder provisioningServlet-technical-domain or provisioningServlet-embedded-technical-domain, respectively,

Update Tomcat and Java Environment

This version runs with Java SE 11 only.It supports Tomcat version 9 only.

Perform these steps:

  • Check your installed Java version.If version 11 is not yet installed, download this version with the latest security fixes and install it.

  • Check your installed Tomcat version.If it is not a supported version, download a supported version with the latest security fixes and install it.Use the Java 11.

  • Configure each Tomcat you designed for deployment of DirX Identity Web Applications so that it uses Java 11 at runtime.

Service Configuration Cleanup Linux

DirX Identity Java-based Worker Containers have been supported with DirX Identity Versions 8.2 but they are no longer supported with this version.

Please check whether these conditions are true:

  • If your installation is an upgrade installation of these DirX Identity versions.

  • You have already executed the integration utility updrcs-linux.sh in the folder install_path/etc in order to integrate start/stop scripts into the operating system.An indication for this is the existence of the file updrcs-linux.sh.log in the same folder.

If these conditions are true, run the steps described in the section “Undoing the Integration” in the section “Integrating Start/Stop Scripts into the Linux Operating System” of the chapter “Configuring DirX Identity” of the DirX Identity Installation Guide.Here, the relevant document set is the one that corresponds to the DirX Identity version you intend to upgrade.