Post-Upgrade Tasks for the New Installation¶
After importing the settings and metadata into the Denodo Platform 8.0, follow these steps:
If you do not use a module, skip its post-upgrade tasks.
Common to All Components¶
Configure the Connection to the Denodo Security Token Server¶
In all the installations of the Denodo Platform - not the Solution Manager - do this:
in the file
<DENODO_HOME>/conf/SSOConfiguration.properties, set these properties:
We recommend enabling HTTPS on the web container of the Solution Manager but if you did not, in the property
sso.url, the port is 19090 instead of 19443.
Restart the server components of the Denodo Platform for this change to apply.
This change is necessary so the components of the Denodo Platform can reach the Denodo Security Token Server, which is part of the Solution Manager.
In Denodo 7.0 this was not necessary but it is in 8.0.
In the databases where you enabled VCS, push the changes to the new repository.
Query at least one base view of each data source to validate the connection to the source.
Execute views that have the cache disabled so the query hits the source and not the cache database.
If a connection to a source fails, it may be because the connection requires an SSL certificate that needs to be imported to
If a connection to a secure LDAP source fails (possibly with a
No subject alternative DNS name matching <HOSTNAME> founderror), check this article in the Denodo Knowledge Base.
If you got a warning indicating that one or more views were using the parameter
QUERYPLAN, do this:
Enable the cost-based optimizer.
Gather the statistics of this view and the subviews of this view.
Obtain the query plan of the view to see if it is the same it was indicated by the parameter “QUERYPLAN”.
Views with cache mode full: if you configured the cache engine of the version 8.0 to use a different catalog/schema, the cache of the views with mode full or partial - explicit loads is empty. Therefore, the queries to these views will return 0 rows. You either need to run the Scheduler jobs that load the cache of these views (if you have them) or load them manually.
Execute this to find the views whose cache needs to be loaded:
SELECT database_name, name FROM get_views() WHERE view_type IN (0, 1) AND cache_status in (3, 4, 5);
To load the cache of these views from the VQL Shell, follow these steps. Note that doing this may take a long time. During this time, you cannot close the tab VQL Shell of the Administration Tool.
Select the check box Retrieve all rows and set Display rows to a high number (e.g. 999999)
Execute this query. This returns the statements to load the cache of the views that require it:
SELECT 'SELECT * FROM "' || database_name || '"."' || name || '" CONTEXT (''cache_preload''=''true'', ''cache_invalidate'' = ''all_rows'', ''cache_wait_for_load''=''true'', ''cache_return_query_results'' = ''false'');' AS query FROM get_views() WHERE view_type IN (0, 1) AND cache_status in (3, 4, 5);
Copy all the rows (click a row of the result and press Ctrl+A).
Paste the rows on the VQL Shell and click Execute to execute all the queries.
These queries will load the cache of the views with mode full or partial - explicit loads.
Materialized tables: when you import the metadata from version 7.0, the materialized tables are created but they are empty. The VQL file includes the metadata but not the data.
Execute this query to obtain the list of materialized tables:
SELECT database_name, name FROM get_views() WHERE input_view_type = 3;
If in the version 7.0, you enabled Kerberos authentication in Virtual DataPort, it is now enabled in version 8.0.
If during the upgrade process, you created a new Kerberos Service Principal Name (SPN) for this installation, open the Kerberos configuration of this Virtual DataPort and change the SPN and upload the new keytab file.
In the subsection Kerberos of the page Preparing to Upgrade, we discuss when you need to create a new SPN.
DenodoConnect components: the VQL file obtained from Virtual DataPort 7.0 includes the DenodoConnect components you had installed. As you have imported this file, their functionality is also available in your Denodo 8.0 server because the DenodoConnect components for Denodo 7.0 are compatible with Denodo 8.0.
There is a new version of the DenodoConnect components specific for 8.0. You can download them from DenodoConnects - 8.0. To import them, open the wizard of the menu File > Extensions management. In the tab Extensions, click Import. You will have to confirm that you want to replace the existing extensions.
Although it is not required, we recommend upgrading the DenodoConnect components with the ones specific for the version 8.0 because in the future, there may be enhancements that are added to DenodoConnect components for version 8.0 but not for the previous versions.
In the databases where you enabled VCS, push the changes to the new repository.
In the client applications that connect to Virtual DataPort 8.0, upgrade the JDBC driver they use to connect to Denodo.
The driver is not compatible across major versions. I.e. you cannot use the JDBC driver of the 8.0 version to connect to previous major versions of Denodo nor use the JDBC driver of a previous version to connect to Denodo 8.0.
If in your applications, the connection URL to Denodo has the parameter “reuseRegistrySocket”, remove it. Otherwise, the connection will fail. This parameter has been removed (see more about this in the section JDBC Driver: Property reuseRegistrySockets of this guide).
Whenever is possible, configure the ODBC clients to use the Denodo ODBC driver instead of the PostgreSQL driver. The performance of the new driver is better.
Increase the Memory Allocated to the Tomcat of Denodo Platform¶
We strongly recommend increasing the amount of memory allocated to the Tomcat of Denodo Platform. To be on the safe side, we suggest doubling the amount of memory. This is necessary because the REST web services of Denodo, now use more memory.
To do this, log in to the Administration Tool or Design Studio and execute the following query. This returns the arguments passed to the Java Virtual Machine (JVM) that runs the Tomcat of the Denodo Platform.
CALL GET_PARAMETER('java.env.DENODO_OPTS_START', 'true');
Copy the value returned by this statement and modify the value of the argument
WEBCONTAINER SET 'java.env.DENODO_OPTS_START' = '-Xmx2g -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -Dorg.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true';
If you want to allocate four gigabytes of memory, put
-Xmx4g instead of
-Xmx2g (you can put the number of gigabytes you want but we strongly recommend to never be higher than 16).
Restart Virtual DataPort to apply this change.
Virtual DataPort Administration Tool¶
Changes to the Virtual DataPort Administration tools:
If in the administration tools of the previous version you increased the query timeout, do the same in the administration tools of the new version.
If you enabled Kerberos authentication, you have to enable it in the administration tools as well.
After importing the metadata to the new version of the Server, if the previous installation is configured to use Kerberos to authenticate users, the new installation will be configured to do that as well.
Log in to Data Catalog with an administrator account.
Data Catalog: Update the URL of Virtual DataPort¶
In Administration > Set-up > Server, enter the URL of Virtual DataPort 8.0.
Data Catalog: Update the URL to the Index Server¶
In Administration > Set-up > Content Search, check that the right Index Server is configured. If you use Scheduler Index, enter the URL of Scheduler Index 8.0.
Data Catalog: Synchronize Metadata¶
Click Administration > Synchronize with VDP Server to synchronize the metadata.
Data Catalog: Configure the Gathering of Statistics¶
If you periodically gather the usage statistics of Data Catalog 7.0, configure the new version to do the same. The section Usage Statistics of the Data Catalog Guide explains how to do this.
Data Catalog: Kerberos¶
If you created a new Kerberos Service Principal Name (SPN) for this installation of Denodo, open the Kerberos configuration of this Virtual DataPort and change the SPN and upload the new keytab file.
If in the version 7.0, you installed DenodoConnect plugins for Scheduler, download these plugins from the Denodo Support Site, for the new version 8.0. Then, remove the existing plugins and import the new ones.
If you created a new Kerberos Service Principal Name (SPN) for this installation of Denodo, open the Kerberos configuration of Scheduler and change the SPN and upload the new keytab file.
Scheduler Index: Copy the Index Files¶
Copy the content of the directory
Scheduler Index: Configure the Indexes¶
In the Scheduler Administration Tool, click the menu Administration > Index server > Indexes. Edit each index to update the directory where the index is located.
Solution Manager: Active Monitors¶
If you have monitors that are active permanently, active them in the new version.
Solution Manager: Kerberos Configuration¶
If you enabled Kerberos on the Solution Manager 7.0, copy the following files to your Desktop:
The keytab file of the Solution Manager 7.0.
If you use a custom
krb5file, copy it as well.
Then, log in to the Solution Manager 8.0 and enable Kerberos using these files.
You can only use the same keytab if the new version is installed on the same host or if the client applications will access through the same alias in the load balancer. That is because, the SPN of the keytab has to match the host name of the URL that the client applications use to connect to Virtual DataPort, Data Catalog, etc. Otherwise, you need to obtain a new keytab for the new computer.
This assumes that you use the same keytab for all the components of the Denodo Platform, which is the usual scenario.
If you enabled Kerberos in Virtual DataPort or Scheduler but not the Solution Manager, you do not have to do this. That is because their Kerberos configuration is transferred when importing the metadata of the version 7.0 into the new version.
External Applications: Upgrade the JDBC Driver¶
In the applications of your organization that connect to Denodo using the JDBC driver, replace the driver with the new driver of Denodo 8.0. The Denodo JDBC driver is not compatible across different major versions. That is, the driver of version 8.0 cannot connect to version 7.0 and the driver of 7.0 cannot connect to 8.0.
The JDBC driver of Denodo 8.0 is available in the Denodo Community (Home / Drivers / JDBC).
We recommend doing the same with the ODBC driver but it is not mandatory.