Pre-Upgrade Tasks for the New Installation

This section lists the tasks you have to complete in the new installations of the Denodo Platform 8.0 and the Solution Manager 8.0, before importing the settings and metadata from the previous version.

If you do not use a module, skip its pre-upgrade tasks.

Common to All Modules

The tasks common to all modules have to be done in the installation of the Solution Manager and in the installation of the Denodo Platform.

Enable SSL

Enable SSL on all the components. You can obtain a new private key or reuse the existing one.

To reuse the existing one:

  1. Copy the file with the private key from the installation of the Denodo Platform 7.0. To locate this file, open the file <DENODO_HOME_7_0>/conf/vdp/VDBConfiguration.properties} and search the property com.denodo.security.ssl.keyStore. Copy the file of this property to the new installation.

  2. Export the public key of this private key and import it into <DENODO_HOME_8_0>/jre/lib/security/cacerts.

    Do not copy the cacerts file from the previous version to the new one. That is because you will not have the most recent certificates of the public Certification Authorities (CA), which will prevent Denodo from connecting to some third-party HTTPS services.

  1. Enable SSL on all the components. We suggest you use the new Denodo SSL/TLS 構成スクリプト. This script automatically modifies all the configuration properties of all the components of the installation of the Denodo Platform and Solution Manager. However, you can still do it manually as in version 7.0.

Configure Windows Services

If you installed the new version on Windows and all/some components run as Windows services, configure these services appropriately. The section Windows サービスの構成 of the Installation Guide explains how to do so.

Copy Krb5 File

  1. In your installation of Denodo 7.0, check if in the directory <DENODO_HOME_7_0>/jre/lib/security there is a file named krb5.conf (on Linux) or krb5.ini (on Windows).

  2. If you have this file, copy it to the installation of Denodo 8.0, to the directory <DENODO_HOME_8_0>/jre/conf/security.

    Even if you did not enable Kerberos authentication on Virtual DataPort, you have to do this in case you were accessing to databases with Kerberos authentication.

    注釈

    The default location of the krb5 file within the Java Runtime Environment (JRE) is different than in previous versions of Denodo. That is because Denodo 8.0 uses Java 11 and previous versions of Denodo, use older versions of Java, which look for this file on a different directory.

  3. Do the same for the Solution Manager (i.e. <SOLUTION_MANAGER_HOME_7_0>/jre/lib/security/).

注釈

Do not enable Kerberos authentication in your new installation of Denodo 8.0 now. During the upgrade process, you will export the metadata and settings of Virtual DataPort of 6.0 or 7.0. This will include the Kerberos configuration and the Kerberos keytab itself. Later, you will import all this into version 8.0.

Virtual DataPort

Virtual DataPort: JDBC Data Sources that Use the Bulk Data Load API

Jump to the next subsection if you installed the new version on the same computer as the version 7.0 or 6.0.

Open each JDBC data source and in the Read & Write tab, check if the check box Use Bulk Data Load is selected and if the field Work path points to a file. In this case and if you installed the Denodo Platform 8.0 on a different computer than 7.0, install the client libraries of this database on the new computer.

If you have a data source with bulk load enabled that connects to one of these databases, consider that in Denodo 8.0, you can configure them so you do not need to download the Hadoop distribution.

  • Hive 2.0

  • Impala

  • Presto

  • Spark

See more about this in the section データの一括読み込みにおける Hadoop ディストリビューションの不要化 of the New Features Guide.

Virtual DataPort: Enable the Cache Engine

If in the current Virtual DataPort you enabled the cache engine, do it in version 8.0 as well.

The previous section Virtual DataPort: Select a Catalog/Schema for the Cache Engine explains the advantages and drawbacks of using the same catalog/schema for the cache engine of version 7.0 and 8.0, or a different one.

After enabling the cache engine, compare the VQL of the data source vdpcachedatasource (database admin) of the version 7.0 and 8.0 to check they are equivalent.

Cache Configuration of Databases

You have to do the same for the Denodo databases that have their own cache configuration.

  1. In the version 7.0, execute this query to obtain the list of databases that have their own cache configuration:

    SELECT DISTINCT database_datasource_name, datasource_name
FROM GET_CACHE_CONFIGURATION()
WHERE datasource_name = 'customvdpcachedatasource';

    If this query does not return any row, it means that all the databases use the global cache configuration.

  2. For each row, do these steps in the version 8.0:

    1. Create a database with the name of the column "database_datasource_name".

    2. In this database, enable the cache configuration as in the version 7.0. Note that, as you did for the global cache configuration, you may also need to choose a different catalog/schema.

Cache Configuration that use the "Generic" Adapter

If the cache engine is configured to use the “Generic” adapter, copy the files cacheConfig-generic.xml and cacheConfig-generic-unicode.xml of the directory <DENODO_HOME_7_0>/conf/vdp to the directory <DENODO_HOME_8_0>/conf/vdp.

Virtual DataPort: Install Third-Party Connectors

In the next step of the upgrade process, when you export the metadata of Virtual DataPort, the resulting file will include the JDBC drivers that your JDBC data sources use. However, you still have to manually install other connectors.

If in Denodo 7.0 you have any of the following elements, install their connector in the new version:

注釈

In this new version, the installation process of these connectors has changed, except for VCS. Instead of copying the files to the installation, use the Administration Tool to install these connectors.

Virtual DataPort: Other Third-Party Jar Files

Go to the folder of your existing Denodo 7.0 installation <DENODO_HOME>/extensions/thirdparty/lib. By default, this folder includes these files:

  • denodo-vdp-jdbcdriver.jar

  • derbyclient.jar

  • jtds.jar

  • ojdbc14.jar

  • postgresql.jar

If you have more files, it means that there are or there were extensions of Virtual DataPort that require these files. Follow these steps to import these files in Denodo 8.0:

  1. Copy the additional files - not the ones listed above - to your computer.

  2. Open the Administration Tool of Virtual DataPort 8.0.

  3. Log in with an administrator account.

  4. Click the menu File > Extensions management. In the tab Extensions, click Import.

  5. In Resource type, select jar and click Add. Note that the files listed in this "explorer" are the files of your computer, not the computer in which Virtual DataPort runs. Select the files with extension "jar" that you just copied from Denodo 7.0.

  6. Click Ok and then, click Ok again to upload these files to Virtual DataPort.

  7. If some of the files you copied from Denodo 7.0 have the extension "dll" or "so", click Import again but this time, in Resource type, select library.

To see what you have imported in the dialog Extensions management, select General in the box Type.

注釈

Do not import in to Denodo 8.0 the files of the connector you just installed in the previous version (in Virtual DataPort: Install Third-Party Connectors).

Virtual DataPort: Version Control System

If you use the Version Control System (VCS) support, change the VCS settings to point to the new repository.

Virtual DataPort: Delete Unused Objects

In the version 7.0, before exporting the metadata, consider removing objects that are not in use anymore. E.g. data sources without views, views and databases that were created for testing, etc.

Virtual DataPort: Delete Aracne and Google Search Data Sources

The Aracne and Google Search data sources were deprecated in the version 7.0 and have been removed from version 8.0. If you have any, you can either delete them now, before exporting the metadata of Virtual DataPort, or delete them later, from the VQL file you generate from Denodo 7.0.

To obtain the list of data sources of these types, execute this query:

SELECT * FROM get_elements()
WHERE input_type = 'DataSources' AND (subtype = 'gs' or subtype = 'arn');

It is easier to do it now, from the administration tool rather than modifying the VQL file later. That way, if you delete a data source, its base views and their derived views will be automatically deleted as well.

Data Catalog: Enable the External Database

If you configured the Data Catalog 7.0 to use an external database, do this:

  1. Copy the JDBC driver of the external database to the new installation. That is, copy the content of <DENODO_HOME_7_0>/lib/data-catalog-extensions to the directory <DENODO_HOME_8_0>/lib/data-catalog-extensions.

  2. Enable this feature. Note that you need to use a different catalog/schema for the new version.

    The section Data Catalog での外部データベースの使用 of the Data Catalog Administration Guide explains how to do this.

Scheduler: Enable the External Database

If you configured Scheduler 7.0 to use an external database, do this:

  1. Copy the JDBC driver of the external database to the new installation. That is, copy the content of <DENODO_HOME_7_0>/lib/scheduler-extensions to the directory <DENODO_HOME_8_0>/lib/scheduler-extensions.

  2. Enable this feature. Note that you need to use a different catalog/schema for the new version.

    The section Use an External Database for Scheduler of the Scheduler Administration Guide explains how to do this.

Solution Manager

Solution Manager: Enable the External Database

If you configured Solution Manager 7.0 to use an external database, do this:

  1. Copy the JDBC driver of this database to the new installation. That is, from <DENODO_HOME_7_0>/lib/solution-manager-extensions to <DENODO_HOME_8_0>/lib/solution-manager-extensions.

  2. Enable this feature. Note that you need to use a different catalog/schema for the new version.

Solution Manager: High Availability

If you had set-up a secondary node of License Manager, do the same for the new version.

Solution Manager: Enable Git Support

If you use the Git support of the Solution Manager, enable it in the new version. Remember to point to the new repository or the new branch.