The OneCloud BizApp for Oracle Essbase streamlines the integration and management of on-premises Essbase cubes with other systems co-existing in the cloud or on-premises. OneCloud provides easy out-of-the-box commands to orchestrate important Essbase operations, including high-speed data load and extract, execution of calculations, and system settings management. When combined with OneCloud’s support for other technologies, the cloud becomes seamless from an application perspective.

Connection Setup

OneCloud connects to Oracle Essbase via the published Java API. To automate functionality within an Oracle Essbase environment from OneCloud, 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, select the appropriate Runner, and use the Oracle Essbase Connections Parameters to complete the setup.

Oracle Essbase Requires Access to the Following Essbase Client JAR Files:

  • ess_es_server.jar

  • ess_japi.jar

  • ess_maxl.jar

Files may be Located Where Oracle Essbase is Installed

Default location as follows:

  • Microsoft Windows:

  • Linux: /User/<username>/Oracle/Middleware/EPMSystem11R1/common/EssbaseJavaAPI/

πŸ““ Same Server
Configure a OneCloud GroundRunner to interact with Essbase on the same server. If the installation of GroundRunner is on the same server as the server hosting Oracle Essbase, then set the Java API Path to the Essbase client Jar files' folder location.

πŸ““ Remote Server

Configure a OneCloud GroundRunner to interact with a remote Essbase server.

If the installation of GroundRunner is on a different server than the server that 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.

Connection Example

The following is an example of a working Connection. Please substitute your own values.

πŸ’‘ Remember to activate the Connection for the desired Environments.

πŸ““ Embedded Mode

The Embedded Mode option should be used only when Oracle EPM products are installed with the "Embedded Mode" option, which is typically used for standalone Hyperion environments.

πŸ““ URL Instance

The Instance URL is the path:port to the Essbase Provider Services. The port is often times different than Essbase itself. In a typical defaulted EPM deployment the port is 19000.

⚠️ This BizApp requires the installation of a Java runtime. For best system compatibility please install Java 8.

Did this answer your question?