To take advantage of the aggregation power of Essbase, Oracle BI EE allows users to deploy Essbase cubes from the Oracle BI EE Essbase Cube Generation module.
In the Essbase Cube Generation module, users define measures, dimensions, and attributes, and then specify cube building options to deploy an Essbase cube. Essbase Studio serves as a web service to help Oracle BI EE deploy Essbase cubes. During the cube deployment process, Oracle BI EE sends an XML file which defines data source information and the cube schema with expected Essbase artifacts, along with deployment options to Essbase Studio. Essbase Studio then deploys the Essbase cube and returns the deployment results back to Oracle BI EE.
When an Essbase cube is deployed from Oracle BI EE, two elements are created in the Data Source Navigator in Essbase Studio Console:
An Essbase connection element.
This is the target Essbase Server connection to which the cube from Oracle BI EE is deployed. This object is prefixed with Essbase and the format is:
Essbase_<server>_<timestamp>
<server>—the Essbase Server name specified in the Oracle BI EE XML (the server attribute of the targetConnection node).
<timestamp>—the generated timestamp for the operation in the time format:
MM-dd-yy_HH-mm-ss
An Oracle BI EE data source connection object.
This is the data source connection of the Oracle BI EE Business Model from which the cube is defined. This node is prefixed with OBIEE.
Since each Essbase cube deployment from Oracle BI EE must be differentiated in the Data Source Navigator, the naming convention for the nodes appear in this format:
OBIEE_<server>_<rpdFileName>_<timestamp[_source$srcNum]>
<server>—the Oracle BI EE server address.
<rpdFileName>—the Oracle BI EE RPD file name.
<timestamp_[_source<srcNum>]>—the generated timestamp for the deployment in the time format:
MM-dd-yy_HH-mm-ss
For each redeployment, new Oracle BI EE data source connection nodes are created. Connection names are differentiated by appending _source<srcNum> to the connection string, and incrementing <srcNum> by 1 for each redeployment. If this is the first deployment, nothing is appended.
Work with Oracle BI EE data source connections created in this way as you would any Oracle BI EE data source connections that you create in Essbase Studio.
See also Working with the Metadata Elements of an Essbase Cube Deployed by Oracle BI EE.