This document is aimed at Denodo users that require to be ready to work with Denodo 7.0. In this document users can find the changes included in Denodo 7.0 and the links to the documentation regarding those news. In addition, this document provides the keys to install Denodo 7.0.
For a quick start guide on how to install and set up the Solution Manager see: Denodo Solution Manager: First Steps.
The Solution Manager is a new component to help administrators manage Denodo deployments. The three main goals are:
The Solution Manager provides a desktop tool: Denodo Platform Control Center, from where it is possible to launch the Solution Manager Components:
The Web Panel is a web application that provides a single point of entry to all the Denodo web tools. This will facilitate users to access all the available tools (Data Catalog, Scheduler Administration tool, Diagnostic and Monitoring tool and Solution Manager). It can be installed along with the Solution Manager.
The Web Panel is designed to be used with Kerberos SSO. By configuring Kerberos authentication in the tools the Web Panel will allow SSO facilitating the authentication process to the users.
The Data Catalog is the “Information Self-Service Tool” (already included in Denodo 6.0) improved. The Data Catalog has been revamped to make it more powerful. It integrates data catalog with data delivery.
The Data Catalog synchronizes its metadata about databases, views and web services with one or several Virtual DataPort servers and stores them locally (it can be synchronized at any moment). This way, the searches in the catalog are faster. It shows information about web services as well as views, and it allows to execute the REST web services.
There are several new features common to all the modules of the Denodo Platform 7.0.
The Denodo Platform Control Center, has been redesigned. This redesign, makes it more user friendly and faster.
Denodo ships now with the Java Runtime Environment (JRE) version 8 (the Denodo servers and its tools cannot run with earlier Java versions).
In addition, it has been added support for Windows Server 2016 and the Denodo OData 4.0 Service has been included in the Denodo distribution.
The Denodo installation has changed slightly in Denodo 7.0. Among the new features of the installer Denodo 7.0 includes a new installer: Denodo Solution Manager installer (denodo-install-solutionmanager-7.0) which includes the Web Panel, Solution Manager and License Manager.
The new features of Virtual DataPort in Denodo 7.0 include changes in data sources, execution engine, Denodo stored procedures, Web Services, Administration Tool, drivers and changes regarding the administration of privileges and monitoring.
As highlighted feature Denodo now has a native data source to Salesforce. It can perform queries and insert, update and delete records in a Salesforce account.
It is also important to mention the changes in the Execution Engine:
Besides the other new features of scheduler, as the Aracne module has been deprecated, Scheduler has a new component for indexing (functionality of the ARN-Index/Search Engine Server) renamed to Scheduler Index.
This way, the Scheduler Administration Tool does not allow creating new instances of the following deprecated elements (but it still allows editing and using the existing ones):
The embedded web container has been upgraded to Apache Tomcat 8.5. This version provides more stability, better performance and better memory management than the version included in earlier versions of Denodo.
Besides the version upgrade there are other minor changes regarding new features of the Embedded Web Container that can be found in the documentation of Denodo 7.0.
Starting with Denodo 7.0, the Aracne module has been deprecated. Besides the Aracne module the following features are currently deprecated in Denodo Virtual DataPort 7.0.
Denodo 7.0 includes three installers:
The above image shows a generic architecture using the new Solution Manager.
The Solution Manager should not be installed in the same host as other Denodo instances. The reason is that when you promote changes, you may switch off some of the Servers of the cluster. However, you want the License Manager to attend requests at all times, from all the other Denodo servers of all environments of the organization.
The Solution Manager contains a Virtual DataPort Server, however, it is not intended to be used as another regular Denodo instance. The Virtual DataPort server installed with the Solution Manager is used just for two things:
The above image has three environments: development, testing and production. Each environment has a Virtual DataPort Server or a cluster of servers with a balancer. The solution Manager is installed in another host and it is used to define and manage the three environments, using the Solution Manager Administration Tool.
As the licenses of all the Denodo servers are managed from just one place (the Solution Manager), administrators will now get a single license file that contains all the licenses of the organization. Therefore, it is necessary to install the global license in the Solution Manager: the centralized place for license management.
When a Denodo component starts, it requests permission to run to the License Manager.
If approved, the server starts and periodically, it requests permission to keep running. Only server components request a license, not client applications. I.e. the Virtual DataPort Administration Tool does not connect to the License Manager because it does not need a license. More information about how licenses work can be found in the Denodo 7.0 documentation.
In order to request that permission to run, for each node we need to define the connection to the License Manager:
As a summary of the installation process, it requires to follow the steps below:
Denodo 7.0 can also be installed as unique Server (like in previous versions) without the Solution Manager. In that case, each Server requires a license as before:
Due to some changes added in Denodo 7.0, before importing the VQL file it may be needed to modify the metadata.
The following properties must be removed:
The property “com.denodo.security.ssl.enabled” controls if SSL is enabled on the Virtual DataPort server. We remove this property to avoid enabling SSL until the migration process is completed.
There are also some considerations regarding the cache and some specific actions when migrating from 5.5 or 5.0. Therefore, please, read the Migration Guide before the migration.