Export the Metadata of the Current Installation¶
Note
You only need to export the metadata of the modules that you installed in the current setup of the Denodo Platform.
Install the latest Denodo Platform update on the current installation.
If you do not want to install permanently the latest update on the current installation, follow these steps:
Make a copy of the folder of the current installation.
Install the latest update.
Perform the steps explained in this section.
Delete the folder of the installation with the latest and put back in place the folder copied in step a.
If you are upgrading from Denodo 5.5 or Denodo 5.0, start the Virtual DataPort server and its administration tool. Log in as an administrator user and execute this command:
SET 'com.denodo.vdb.catalog.exportMigrationCompatibility' = 'true';
Denodo 6.0 introduces minor changes to the VQL syntax to avoid ambiguities in the process of parsing VQL statements. These changes are not backwards compatible with earlier versions.
Adding this property instructs Virtual DataPort to generate VQL statements that are compatible with Denodo 6.0. Later in this process, you will have to remove this property to keep generating VQL statements with the “older” syntax.
The section Changes in VQL Syntax lists these changes.
This property is only useful when upgrading from Denodo 5.5 or 5.0. It does not do anything in Denodo 4.7 or earlier versions.
Start all the servers of the current installation. If Virtual DataPort was already started, restart it to apply the change of the previous step.
Export the metadata of Virtual DataPort and the ITPilot’s Wrapper server using the export script of the current installation. To do this, open a command line and execute the following:
cd <OLD_DENODO_HOME>/bin export --login <login of an administrator user> --password <password> --server localhost:9999 -f export.vql -P includeJars=yes -P includeScanners=yes -P includeCustomComponents=yes -P includeStatistics=yes -P includeDeployments=yes -P dropElements=yes -P excludeServerConfigurationProperties=com.denodo.vdb.vdbinterface.server.VDBManagerImpl.registryURL,com.denodo.vdb.vdbinterface.server.VDBManagerImpl.registryPort,com.denodo.vdb.vdbinterface.server.VDBManagerImpl.shutdownPort,com.denodo.vdb.vdbinterface.server.VDBManagerImpl.factoryPort,com.denodo.vdb.vdbinterface.server.VDBManagerImpl.odbcPort,com.denodo.vdb.cache.cacheMaintenance,java.env.DENODO_OPTS_START,java.env.DENODO_OPTS_STOP,com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.enableAutoSingleUserMode,com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.strictAutoSingleUserMode,com.denodo.vdb.catalog.exportMigrationCompatibility -P excludeWebContainerConfigurationProperties=com.denodo.tomcat.jmx.rmi.port,com.denodo.tomcat.http.port,com.denodo.tomcat.shutdown.port,com.denodo.tomcat.jmx.port,java.env.DENODO_OPTS_START,java.env.DENODO_OPTS_STOP
If you already created metadata (data sources, views, etc.) on the Virtual DataPort server version 6.0, replace
dropElements=yes
withreplaceExistingElements=yes
.If you are upgrading from Denodo 5.5 or Denodo 5.0, open the file
<OLD_DENODO_HOME>/conf/vdp/VDBConfiguration.properties
again, remove the property added in step 2 (com.denodo.vdb.catalog.exportMigrationCompatibility
) and stop Virtual DataPort.Stop Virtual DataPort because changes to this property only take effect after restarting.
Export the metadata of ITPilot Wrapper Generation Tool: Use the File > Export option of the Wrapper Generation Tool.
Read the section Migrating Wrappers Between Generation Environments: Import and Export of the ITPilot Generation Environment Guide for more information about this.
Export the metadata of Scheduler: use the
export
script located in<OLD_DENODO_HOME>/tools/scheduler
.Read the section Use of the import/export scripts for backup of the Scheduler Administrator Guide for more information about this step.
Export the metadata of Aracne: use the
export
script located in<OLD_DENODO_HOME>/tools/arn-index
.Read the section Use of the import/export scripts for backup of the Aracne Administrator Guide for more information about this step.