This article has expired. Please visit the OneCloud Knowledge Base for the latest documentation.
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 protected].
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
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. Also, the Instance URL will be
Configure a OneCloud GroundRunner to interact with a remote Essbase server
If the installation of GroundRunner is on a different server from the server 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.
An Essbase command is executed and the output is blank.
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 the following error
Exception in thread "main"  false} stdErr="java.lang.NoClassDefFoundError: com/essbase/api/base/EssException"
Please be sure to follow the connection setup that requires the Essbase JAR files.
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.
- Ensure that the specified server name is correct and is the provider server. Please do not use the IP address and port number of your Essbase server unless they are on the same operating environment.
- Ensure that the specified port number is correct. The default port for provider services is
Error: com.essbase.api.base.EssException: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1042003): Network Error : 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 : Failed to retrieve name information for [Essbase-Cluster1]
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.
Updated 4 days ago