Bridge Specifications
| Vendor | Oracle |
| Tool Name | Oracle Hyperion Essbase Integration Services (EIS) |
| Tool Version | 7.x to 9.x |
| Tool Web Site | http://www.oracle.com/technetwork/middleware/essbase/overview/index.html |
| Supported Methodology | [Business Intelligence] BI Design (RDBMS Source, Dimensional Target, Transformation Lineage) via XML File |
SPECIFICATIONS
Tool: Oracle / Oracle Hyperion Essbase Integration Services (EIS) version 7.x to 9.x via XML File
See http://www.oracle.com/technetwork/middleware/essbase/overview/index.html
Metadata: [Business Intelligence] BI Design (RDBMS Source, Dimensional Target, Transformation Lineage)
Component: HyperionEis version 11.2.0
OVERVIEW
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at https://www.metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html
SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | |||
| File | This bridge generates an XML file. Use Hyperion Essbase Integration Services to load the content of the XML file. 1. Choose 'XML Import/Export...' from the 'File' menu. 2. Select the 'Import' tab. 3. Click on the 'Open XML File' button to select the file you want to open. 4. Click on the 'Import to Catalog' button. |
FILE | *.xml | Mandatory | ||||
| Data model EIS Data source | Name of the EIS data source to be used. | STRING | Mandatory | |||||
| Data model Relational Schema name | The relational tables definitions in the model to be exported may not always specify the owner schema name where they are stored in the database and this option allows to specify where they are located. | STRING | Mandatory | |||||
| Dimensional Schema name | Allows to specify in which schema the new dimensional objects should be created. | STRING | Mandatory | |||||
| Dimensional modeling detection | When using this bridge to convert a data model created in a data modeling or ETL tool and forward engineer it to an OLAP/BI model, the dimensional role that has been specified for each table (fact, dimension, outrigger) is used by the bridge to infer how those tables are converted into BI facts and dimensions. This parameter controls how the tables dimensional role (fact, dimension, outrigger) is to be detected, even if the source model did not specify tables dimensional role. 'As defined by source model' Use the tables dimensional role if defined by the source model. 'Autodetect from relational schema' Automatic detection of fact and dimension tables, based on foreign keys. This algorithm considers tables with only incoming foreign keys as fact tables. Tables with outgoing foreign keys are considered dimension tables or outrigger tables depending on the minimum distance (number of foreign key relationships) to a fact table. Tables with no foreign key relationships to any other tables are considered as dimension tables. 'Manually specified Facts and Dimensions' Manually specify the fact and dimension tables. 'Disabled' No forward engineering to OLAP occurs. |
ENUMERATED |
|
As defined by source model | ||||
| Dimensional modeling detection Fact tables | When using this bridge to convert a data model created in a data modeling or ETL tool and forward engineer it to an OLAP/BI model, the dimensional role that has been specified for each table (fact, dimension, outrigger) is used by the bridge to infer how those tables are converted into BI facts and dimensions. You can specify the list of fact tables of your model in this option, and the bridge will consider them as a fact when generating dimensions and measures, e.g. dbo.Fact1; Fact2 This option is useful if the source tool does not support this notion of table dimensional role, and can be used to work around the limitations of the source tool. The behavior of this option can be combined with the 'Dimensional modeling detection Dimension tables' option, so that some tables are handled as facts and the others as dimensions. |
STRING | ||||||
| Dimensional modeling detection Dimension tables | When using this bridge to convert a data model created in a data modeling or ETL tool and forward engineer it to an OLAP/BI model, the dimensional role that has been specified for each table (fact, dimension, outrigger) is used by the bridge to infer how those tables are converted into BI facts and dimensions. You can specify in this option if the bridge should assume that all tables are dimensions. 'True' The bridge assumes that all tables are dimensions. 'False' The bridge uses the dimensional role specified on each table, if any. Useful if the source tool does not support this notion of table dimensional role, and can be used to work around the limitations of the source tool. The behavior of this option can be combined with the 'Dimensional modeling detection Fact tables' option, so that some table share handled as facts and the others as dimensions. |
BOOLEAN | True | |||||
| XML Indentation (pretty printing) | Controls the pretty printing of XML, for the purpose of opening the generated file in a text editor. E.g. 'space characters' Several space characters as indentation. 'tab key' Tab character as indentation. 'empty' No indentation which leads to a more compact file. |
STRING | ||||||
| Verbosity | Controls the dimensional modeling forward engineering verbosity level. 'False' Normal verbosity. 'True' Additional information is printed in the log. |
BOOLEAN | True |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"Oracle Hyperion Essbase Integration Services (EIS)" Metamodel HyperionEis |
Mapping Comments |
| Attribute | Column | Used to reference the underlying database Column. |
| DesignLevel | Not applicable if LOGICAL_ONLY | |
| Name | Name | |
| PhysicalName | Name | if a business name has been set |
| BaseType | DataType | |
| DataType | DataType | |
| Class | Table | Used to reference the underlying database Table. |
| DesignLevel | Not applicable if LOGICAL_ONLY | |
| Name | Name | |
| PhysicalName | Name | if a business name has been set |
| DatabaseSchema | Schema | Used in the identification of relational tables, for tables with no schema set, it may be provided as bridge option "Relational Schema" Provided as bridge option "Dimensional Schema" to create dimensional objects |
| Name | name | |
| PhysicalName | name | |
| DerivedType | DataType | |
| DataType | DataType | |
| Dimension | FactView, ModelDim, ModelView | The first Fact Dimension is exported as FactView. Related dimensions are exported as ModelDim and ModelView |
| Description | Desc | |
| Name | Name | |
| Type | ModelDimType | The first Fact Dimension is exported as FactView The related Dimensions are exported as ModelDim and ModelView Time Dimensions are marked as Time |
| UserDefined | Non user defined dimensions are not exported | |
| DimensionAttribute | ModelViewMember | |
| Description | Desc | |
| Name | Name | |
| FeatureMap | Model View Member | |
| Operation | Physical Column Name | |
| Measure | ModelViewMember | |
| DefaultAggregation | AggregateType | |
| Description | Desc | |
| Hide | DisplayFlag | |
| Name | Name | |
| SQLViewAttribute | View Column | Used to reference the underlying database View Column. |
| Name | Name | |
| PhysicalName | Name | if a business name has been set |
| SQLViewEntity | View | Used to reference the underlying database View. |
| Name | Name | |
| PhysicalName | Name | if a business name has been set |
| StoreModel | This bridge exports the model's OLAP dimensions and hierarchies. If the current model is relational only, a forward engineering process (from a relational star schema model into an OLAP dimensional model) takes place before the actual export, using the parameters supplied as bridge options. |