Strategy ONE

Relating Objects from Oracle Essbase to Strategy

MDX cube reports from an Oracle Essbase 11.1.2 MDX cube can be treated like standard Strategyreports.

In this section, the term Oracle Essbase is used to refer to Oracle Essbase 11.1.2.

The metadate model translation process involves the following steps:

  1. From Oracle Essbase to XMLA: Oracle Essbase exposes its databases through the XMLA model which is derived from the ODBO model. XMLA defines an object model that is used in conjunction with MDX to query cubes. The Oracle Essbase model pre-dates XMLA so there are some differences. When thinking about Oracle Essbase objects, keep in mind how those objects appear in XMLA.
  2. From XMLA to Strategy: After Oracle Essbase objects are translated into the XMLA model, they are translated into the Strategymetadata model. You can then interact with Oracle Essbase content while working within the paradigm that is consistent with the rest of Strategy's products.

This diagram shows how Oracle Essbase objects are exposed in XMLA and then how they are related to objects in the Strategy environment.

The process for each Oracle Essbase object is described in the following topics: