Help Desk

Submit a ticket My Tickets
Welcome
Login

Oracle Essbase BizApp


Premium BizApp

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

Need a specialized Oracle Essbase Command?

If there are specific Oracle Essbase operations that your company is looking to perform support@onecloud.io to discuss the requirements and the possibility to incorporate the capability into OneCloud.

Connection Setup

OneCloud connects to Oracle Essbase via the published Java API. 

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: 

InputTypeDetail
UsernameTextFieldOracle Essbase username 
PasswordTextFieldOracle Essbase password
Instance URLTextFieldThe base URL of your Essbase Instance. In many cases, it may just be an IP address, proceeded by the proper protocol (i.e. http://100.0.0.1). In other cases, it might be the URL for your APS service (i.e. http://100.0.01:19000).
Cluster NameTextFieldName of the Essbase cluster to which you are connecting. Essbase will call this “EssbaseCluster” by default.
Java API PathTextFieldThe 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: 

  • ess_es_server.jar 
  • ess_japi.jar 
  • ess_maxl.jar

These files can be located where Oracle Essbase is installed and the default location is as follows: 

  • Microsoft Windows:
    C:\Oracle\Middleware\EPMSystem11R1\common\EssbaseJavaAPI\11.1.2.0\lib 
  • Linux:
    /User/<username>/Oracle/Middleware/EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0/lib 

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 CoeCloud 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.

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.

Connection Example

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

Troubleshooting

No output received when running a command

Issue 

An Essbase command is executed and the output is blank.

Suggestion

The OneCloud Essbase BizApp requires a Java Runtime Environment (JRE). Please be sure to install a compatible such as Oracle JRE 1.8.x.

Receive a Java No Class Found Error

Issue 

Receive the following error Exception in thread "main" [] false} stdErr="java.lang.NoClassDefFoundError: com/essbase/api/base/EssException"

Suggestion 

Please be sure to follow the connection setup that requires the Essbase JAR files.

Cannot connect to Provider Services

Error 

Error: com.essbase.api.base.EssException: Cannot connect to Provider Server. Make sure the signon parameters are correct and the Provider Server is running. Error authenticating with Essbase: Cannot connect to Provider Server. Make sure the signon parameters are correct and the Provider Server is running.

Suggestion 

Ensure that the specified server name is correct and is the provider server. Please do not use the IP address and port 2. number of your Essbase server unless they are in the same operating environment. 

Ensure that the specified port number is correct. The default port for provider services is 19000.
Cannot connect to OLAP Service

Error 

Error: com.essbase.api.base.EssException: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1042003): Network Error [11001]: Failed to retrieve name information for [Essbase-Cluster1] Error authenticating with Essbase: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1042003): Network Error [11001]: Failed to retrieve name information for [Essbase-Cluster1]

Suggestion 

Ensure that the Essbase cluster name is correct. In the error message above, the connection is able to communicate with Essbase, but the connection is being rejected since the cluster name is not correct.

B
Brian is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.