Installing the Connector for Oracle Essbase

In order to retrieve data from Oracle Essbase, you have to install its connector.

The Oracle Essbase API provides two modes of connecting to Essbase servers. The section Multidimensional Data Sources to Oracle Essbase of the Virtual DataPort Administration Guide provides more information about these modes.

The set of drivers you have to install, depend on the connection mode used:

  1. Three-tier APS mode: obtain the ess_japi.jar.

  2. Embedded mode: check the Administration Guide of Oracle Essbase to obtain the list of jars that a Java application needs to connect to Essbase in Embedded mode. Make sure that the version of the Essbase Administration Guide matches the version of your Essbase server because the jars required change depending on the release of Essbase you want to connect to.

After obtaining the appropriate jars, copy them to the Denodo installation:

  • Copy the Oracle Essbase version 9 drivers to the directory <DENODO_HOME>/lib/extensions/essbase-drivers/9

  • Copy the Oracle Essbase version 11 drivers to the directory <DENODO_HOME>/lib/extensions/essbase-drivers/11

Requirements of the Essbase 11 Adapter

If you are using 7.0u20210628 or newer, the user account in Essbase requires the role “read”.

If you are using 7.0u20200803 or earlier to connect to Oracle Essbase or newer, the user account in Essbase requires the role “manager (database)”. This is necessary to be able to introspect cubes. That is, to list the contents of the cubes during the process of creating base views. This user account needs this role because by default, the data source opens the outline of the cube.

By default, with the update 7.0u20201116, the user account also requires the role “manager (database)” but you can disable this requirement if you want. To do this, log in to Virtual DataPort as an administrator and execute this command (you do not need to restart after this):

SET 'com.denodo.vdb.essbaseAvoidOpenOutline' = 'true';

With this change, the user account for Essbase only requires the role “read” because it does not open the outline of the cubes. Note that you still need the “execute” role as well to be able to execute queries.

Add feedback