Everything Oracle

Architecture

Before working through the next article on “Essbase Cube Creation”, it will be helpful to have a mental picture of how Integration Services connects to other Hyperion components:

Integration Services Architecture

Objective

Our objective is to create an Essbase Database. Data from this database is served by the Essbase Server, and can be examined using a variety of tools and applications. In our case, we’ll examine it using the Administration Services Console, which is part of Administration Services.

Relational Data Source

The relational data that we need to create the Essbase Database is held in a Data Source (in this case, in an Oracle database), so we need to get Integration Services to retrieve this data and then send it to the Essbase Server to create the Essbase Database.

Metadata Mapping

In order for Integration Services to create the Essbase Database it needs to know how to map the data from a relational format into a multidimensional cube format. The instructions needed to perform this mapping are contained in an OLAP Model and an OLAP Metaoutline, both of which are held in an OLAP Metadata Catalog, which is stored in a relational database (in this case, also in an Oracle database).

ODBC Data Sources

Integration Services can’t connect directly to the relational databases containing the Data Source and the OLAP Metadata Catalog. Instead it needs to do so by means of ODBC data sources.

Note, the Shared Services link in the diagram is put in for completeness since we’ll encounter in on the Integration Services Console Login Page – it’s only needed for versioning, and we won’t make use of it.

Everything Oracle

Home

Everything Oracle