Import Settings and Metadata in to the New Installation¶
Follow these steps to import the metadata of the previous installation to the new one.
If you do not use a module, you do not need to import its metadata and settings.
Do not import metadata nor settings from Denodo 6.0 or earlier. Some VQL statements of 6.0 and previous versions are incompatible with 8.0. The section Upgrading from Denodo Platform 6.0 or Earlier explains how to proceed in this scenario.
Log in to Virtual DataPort 8.0 with an administrator account.
Click the menu File > Import. In this dialog, select the resources file (
resources_denodo_70.vql) and click Ok.
Open the dialog File > Import again. This time, select the metadata file (
Select Save output and Report only commands that were not executed successfully.
Once the import is completed, open the output file and verify that there were no errors.
If there are errors during this process, check the section below Common Errors when Importing the Metadata of Virtual DataPort 7.0 to 8.0.
Log in to Data Catalog 8.0 with an administrator account and import the file exported from the previous version.
For Scheduler Index, connect to the computer where the Denodo Platform 8.0 is installed, and execute this:
cd <DENODO_HOME>\tools\arn-index import.bat -h localhost -p 9000 -l <user name> -P <password> -f scheduler-index_export_70.zip
cd <DENODO_HOME>/tools/arn-index ./import.sh -h localhost -p 9000 -l <user name> -P <password> -f scheduler-index_export_70.zip
In this command, replace
<password>with the credentials of an administrator user.
scheduler-index_export_70.zipis the result of exporting Scheduler Index 7.0.
Log in to Scheduler 8.0 with an administrator account and import the file exported from the previous version.
The Scheduler 8.0 server must be configured to use the same type of metadata database as the one of the version 7.0 used to export the metadata (i.e. if you have exported the metadata from a Scheduler 7.0 server configured to use Derby as metadata database, you should configure the Scheduler 8.0 server to also use Derby). If desired, after importing the metadata, you can configure the Scheduler 8.0 server to use other type of metadata database.
Log in to Solution Manager 8.0 with an administrator account and do the following:
Import the file exported from the previous version.
Edit the servers so they point to the new Denodo servers. Note that the Solution Manager of 8.0 can only interact with Denodo servers of the same major version (8.0).
Open the ITPilot Wrapper Generation Tool and import the ITPilot wrappers exported from version 7.0.
Common Errors when Importing the Metadata of Virtual DataPort 7.0 to 8.0¶
If you see an error like this:
1 2 3 4 5 6 7 8 9 10 11 12 13
CREATE OR REPLACE DATASOURCE CUSTOM cw_denodo_dfs_customwrapper FOLDER = '/sources/hadoop/hdfs' CLASSNAME='com.denodo.connect.hadoop.hdfs.wrapper.HDFSDelimitedTextFileWrapper' JARS 'denodo-dfs-customwrapper' ERROR:Error creating new data source: Parameter 'File system URI' is mandatory Command: CREATE OR REPLACE DATASOURCE CUSTOM cw_denodo_kafka FOLDER = '/sources/others' CLASSNAME='com.denodo.connect.kafka.wrapper.KafkaDateRangeConsumerWrapper' JARS 'denodo-kafka-customwrapper' ERROR:Error creating new data source: Parameter 'Connection String *' is mandatory
If you get errors like the ones in line #6 and #13 (Parameter … is mandatory), it means that:
This DenodoConnect used to define an input parameter as part of its base views. That version was imported into Virtual DataPort 7.0 at some point.
This applies to any custom wrapper, not just the DenodoConnect ones.
At a later date, this DenodoConnect was replaced in Denodo 7.0 with the current version. In this new version, the parameter has to be set in the data source and it no longer is a parameter of the base view.
Because of this, the VQL generated for this custom wrapper is invalid both for 7.0 and 8.0. At this moment, in version 7.0, the base views created over this custom data source can be queried but if you export the VQL of the custom wrapper and import it again into 7.0, it will also fail. The DenodoConnect components that changed in this way regarding input parameters have post-installation tasks to modify their configuration (i.e. open the ZIP file of the DenodoConnect and look for the post-installation notes in the README file).