Installing Updates, Bugfixes and Extra-Features¶
This section explains how to install Updates, Bugfixes and Extra-features, over an installation of the Denodo Platform. These instructions also apply to the Solution Manager.
Note
In this page, the term “update” will be used to refer to all types of software modifications: Updates, Bugfixes and Extra-features.
See also Best Practices: Deployment of Updates Across Your Organization.
Download the update from the Denodo Support Site. The .zip file of the beta updates include a temporary license so you can install them on a separate environment without interfering with your current installations of Denodo.
There are two ways of installing an update:
The Denodo servers keep backward compatibility regarding Design Studio, their Administration Tools, drivers,…, within the same major version. That is, you can install a newer update in the server without having to install it on the administration tool nor update all the JDBC/ODBC clients (see more about this in the page Backward Compatibility Between the Virtual DataPort Server and Its Clients).
Important
After installing an update in the installation of the Solution Manager, start the License Manager before the Solution Manager server. Otherwise, the Solution Manager server may fail.
Installing an Update Graphically¶
Follow these steps to install an update from the Control Center:
Go to the Support Site, to the page of the update, to read the RELEASE NOTES of the update; pay special attention to the Post-installation actions section (it is in the Support Site, in the Details page of the update).
Decompress the zip file of the update.
Stop all the Denodo servers and tools, in the host where you are going to install the update.
Optionally, make a copy of the entire folder of the Denodo Platform. It is not possible to rollback an update, so this copy will allow you to restore quickly the Platform to its previous state, if necessary.
Before copying the folder, delete the content of these folders to save space:
<DENODO_HOME>/work/vdp/swap
<DENODO_HOME>/work/vdp/pipe
These folders contain information that is not necessary once the Denodo server is stopped.
On production servers, if any of the components is configured to store its metadata and settings on an external database, we recommend making a backup of the catalog of the database where the metadata is stored.
The components that can be configured to store its metadata and settings on an external database are the Solution Manager, Virtual DataPort, Data Catalog and Scheduler.
This recommendation is not about the cache database of Virtual DataPort.
Run
<DENODO_HOME>/bin/denodo_platform
to open the Denodo Control Center.Click Update (on the right wide of the window). This dialog lists the updates that have been installed (the last update of the list is the current one).
Click Install update and select the jar file (not the zip file) of the update. The Control Center will display a dialog with a progress bar.
Installing an Update from the Command Line¶
You can install an update from the command line, without displaying a GUI. This is useful if you want to install an update using a script or in a host without graphical support.
To do this, follow these steps:
Go to the Support Site, to the page of the update, to read the RELEASE NOTES of the update; pay special attention to the Post-installation actions section (it is in the Support Site, in the Details page of the update).
Decompress the zip file of the update.
Stop all the Denodo servers and tools, in the host where you are going to install the update.
Optionally, make a copy of the entire folder of the Denodo Platform/Solution Manager. It is not possible to rollback an update, so this copy will allow you to restore quickly the Platform to its previous state, if necessary.
Before copying the folder, delete the content of these folders to save space:
<DENODO_HOME>/work/vdp/swap
<DENODO_HOME>/work/vdp/pipe
These folders contain information that is not necessary once the Denodo server is stopped.
On production servers, if any of the components is configured to store its metadata and settings on an external database, we recommend making a backup of the catalog of the database where the metadata is stored.
The components that can be configured to store its metadata and settings on an external database are the Solution Manager, Data Catalog and Scheduler.
This recommendation is not about the cache database of Virtual DataPort.
Open a command line. On Windows, launch the command line with the option “Run as administrator” even if you are logged in as an administrator.
Execute the following command:
For Linux:
cd <DENODO_HOME> ./jre/bin/java -jar <path to the JAR file of the update> <DENODO_HOME> -c
For example (Linux):
cd <DENODO_HOME> ./jre/bin/java -jar denodo-v80-update-202102092200.jar "$PWD" -c
For Windows:
cd <DENODO_HOME> .\jre\bin\java.exe -jar <path to the JAR file of the update> <DENODO_HOME> -c
For example (Windows):
cd <DENODO_HOME> .\jre\bin\java.exe -jar denodo-v80-update-202102092200.jar "%CD%" -c
In the commands above, replace <DENODO_HOME>
with the path to the installation of Denodo.
This installs the update in the installation of <DENODO_HOME>
.
If the installer detects that any Denodo server or tool is running, it will ask for configuration to continue. The installer does this to make sure that the update can be installed correctly. Take this into account if you are using a script to install the same update on several hosts.
This command returns one of these exit codes:
0: the update is installed successfully.
1: one or more commands executed during the installation of the update fails.
-1: when any other kind of error occurs.
Troubleshooting the Updates Installer¶
During the installation of an update, there may be unexpected errors that prevent the installation from completing correctly. For example, the user that starts the update does not have enough privileges to modify the installation or, if you are on Windows, another application is blocking a file of the Denodo Platform.
To troubleshoot these problems, install the update from the command line and add the parameter --log-level=DEBUG
. For example:
cd <DENODO_HOME>
./jre/bin/java -jar denodo-v80-update-202102092200.jar <DENODO_HOME> -c --log-level=DEBUG
Once the installation process finishes, open the most recent file of the folder <DENODO_HOME>/logs/update
. This file will contain logging information about the installation process that may help you find the cause of the problem.
The allowed values for the parameter --log-level
are (from more informational to less informational): TRACE
, DEBUG
, INFO
, WARN
and ERROR
.
Note
The installer of updates detects if there were errors during the installation of the previous update. If this happens, the installer of updates will prevent you from installing this new update until you reinstall the previous one correctly. To ignore this restriction, use the command line parameter -force.