The OneCloud BizApp for Oracle Essbase streamlines the integration and management of on-premise Essbase cubes with other systems that co-exist in the cloud. OneCloud provides easy out-of-the-box commands to orchestrate important Essbase operations including high-speed data load and extract, execution of calculations and management of system settings. When combined with OneCloud's support for other technologies, the cloud suddenly becomes seamless from an application perspective.
For documentation on all available commands, see the Oracle Essbase Command Reference.
OneCloud connects to Oracle Essbase via the published Java API. The OneCloud BizApp for Oracle Essbase is compatible with all versions 11.x and greater of Essbase. If you require support for earlier versions of Oracle Essbase (i.e. 7.x or 9.x), please contact email@example.com.
To automate functionality within your Oracle Essbase environment from OneCloud, you'll need to navigate to the connection manager to create a connection.
This connection requires a OneCloud GroundRunner. Learn more about the GroundRunner Configuration
From here, choose Oracle Essbase from the service drop-down and select the appropriate Runner. Now, enter values for the following fields:
Essbase user name
The base URL of your Essbase Instance. In many cases, it may just be an IP address, proceeded by the proper protocol (i.e. http://184.108.40.206)
Name of the Essbase cluster to which you are connecting. Essbase will call this "EssbaseCluster" by default.
Java API Path
The path to your Essbase JAR files. These files are installed by default in your Essbase directory, and the path will contain "EssbaseJavaAPI\VERSION". The full path to the directory containing the .jar files is required.
Oracle Essbase requires access to the following Essbase client JAR files:
These files can be located where Oracle Essbase is installed and the default location is as follows:
- Microsoft Windows:
Configure a OneCloud GroundRunner to interact with Essbase on the same server
If the installation of GroundRunner is on the same server other than is hosting Oracle Essbase, then simply set the
Java API Path to the folder location of the Essbase client Jar files.
Configure a OneCloud GroundRunner to interact with a remote Essbase server
If the installation of GroundRunner is on a different server other than is hosting Oracle Essbase, then copy these files to a new folder on the server that hosts the GroundRunner and set the
Java API Path to this folder.