Version Compatibility
If you use DMC (Deployment Monitoring Console), you may need to update DMC when you update your version of Liquibase Enterprise/Liquibase Business/Datical DB.
To find which versions of DMC can be used with which versions of Liquibase Enterprise/Liquibase Business/Datical DB, expand the Datical DB and Deployment Monitoring Console Compatibility Matrix section at DMC Compatibility Matrix and Release Notes.
DMC
...
Upgrade Instructions
| Info |
|---|
If you have the Java version was manually changed the java version used by DMC, you will need to restore DMC’s DMC's default version of Java (11.0.8) before any time that you upgrade upgrading DMC. Move or copy the previous version of Java (11.0.8) from the /opt/datical/old_jre directory back to the /opt/datical/jre directory prior to starting your DMC upgrade. DMC expects . DMC expects Java version 11.0.8 to be in the /opt/datical/jre directory for the DMC upgrade process to be successful. After your DMC upgrade is complete, you can change the Java version to a different 11.x java version again. For more information, see How to Change the Java version for DMC. |
...
...
. |
...
Log in to software.datical.com. Go to Folders, Common, Datical_DMC_Software, and download the .sh file for the version of DMC that is compatible with your version of Liquibase Enterprise
...
.
Copy the .sh file
...
to your existing DMC server.
Example
datical-service-unix-7_17_243-master.sh
If LDAP is configured (not LDAPS), check LDAP connectivity in keycloak.
Go to https://YOUR_DMC_ADDRESS/auth/
Click on "Administration Console" and enter your Keycloak credentials.
Switch to
...
the "datical" realm and click on "User Federation."
Select your LDAP configuration.
Click “test connection”.
If your LDAP connection is successful, proceed with the next upgrade steps.
If your LDAP connection is unsuccessful, you’ll need to resolve this connection before proceeding with the upgrade.
If LDAPS (LDAP over SSL, with a certificate imported into DMC from LDAP) is configured, you’ll need to disable LDAP in Keycloak.
Go to https://YOUR_DMC_ADDRESS/auth/
Click on "Administration Console" and enter your Keycloak credentials.
Switch to the "datical" realm and click on "User Federation."
Select your LDAP configuration.
In the top right corner, toggle off the LDAP configuration.
Proceed with the next upgrade step. LDAP will be enabled in a later step.
Run the installer with the following command.
Put in the appropriate version number:
Code Block /home/datical> sudo bash /datical-service-unix-<version>-master.sh
...
Example:
Code Block /home/datical> sudo bash /datical-service-unix-7_12_216-master.sh
Enter your existing OS user as the admin user and admin group.
Enter the directory of the previous DMC installation when prompted for an install location.
The installer will update your installation and restart affected DMC services. You can begin using the new version of the DMC immediately.
If LDAPS is configured, you’ll need to enable it again before using DMC.
Go to https://YOUR_DMC_ADDRESS/auth/
Click on "Administration Console" and enter your Keycloak credentials.
Switch to the "datical" realm and click on "User Federation."
Select your LDAP configuration.
In the top right corner, toggle on the LDAP configuration.
Click “test connection”.
If your LDAP connection is successful, you can start using DMC.
If your LDAP connection is unsuccessful, you’ll need to resolve this connection issue.
If you receive a
PKIX path build failedin your Keycloak logs, you’ll need to import your LDAPS certificate into the Java truststore.keytool -import -alias example -keystore /opt/datical/jre/lib/security/cacerts" -file example.cer