Oracle Hyperion Essbase Integration Services (EIS) - Import - Cloud

Talend Cloud Data Catalog Bridges

author
Talend Documentation Team
EnrichVersion
Cloud
EnrichProdName
Talend Cloud
EnrichPlatform
Talend Data Catalog

Note: This bridge is not available in Talend Cloud Data Catalog by default. You need to set up a remote harvesting agent to import metadata from this source. For more information, see Deploying a remote harvesting agent in Talend Cloud Data Catalog Administration guide.

Bridge Requirements

This bridge:
  • is only supported on Microsoft Windows.

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
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection
Data Profiling

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.0.0

OVERVIEW
REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a trouble shooting 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
Olap Model File When an OLAP Model is currently loaded in Essbase Integration Services:

1. Choose 'XML Import/Export...' from the 'File' menu.
2. Click on the 'Export' tab.
3. Select the OLAP Model you are interested in exporting.
4. Type the file name you are saving in the 'Export file name' text box
5. Click on the button labelled 'Save As XML File'.

This bridge will use the generated XML file as input.
FILE *.xml   Mandatory
Metaoutline File When a Metaoutline is currently loaded in Essbase Integration Services:

1. Choose 'XML Import/Export...' from the 'File' menu.
2. Click on the 'Export' tab.
3. Select the Metaoutline you are interested in exporting.
4. Type the file name you are saving in the 'Export file name' text box
5. Click on the button labelled 'Save As XML File'.

This bridge will use the generated XML file as input.
FILE *.xml    
Data model Tables design level This option controls the design level of the imported tables.

It is particularly relevant when exporting metadata to a target tool which supports two views of the model: a logical view and a physical view.

Some Data Modeling tools support this concept, where you can decide if a table appears both as a physical table and as a logical entity.

Some Business Intelligence tools also support this concept, where you can decide if a table appears both in the physical model and in the business view of the model.

'Logical and physical'
If you would like the tables to appear both in the logical view and in the physical view of the model.

'Physical'
If you would like tables to appear only in the physical view of the model.
ENUMERATED
Physical
Logical and physical
Physical  

 

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  
DesignLevel   as defined by the "Table Logical information" bridge option
Name name  
Position   Computed
BaseType Datatype  
DataType   See datatype conversion array
Name   Derived from the datatype
PhysicalName   Derived from the datatype
Class Table  
DesignLevel   as defined by the "Table Logical information" bridge option
Name name  
ClassDiagram   One default diagram is created to display the tables used in the model
Name   set to <Main Subject Area>
ClassifierMap Join, Dimension Used to hold the traceability, via FeatureMap objects
Condition Join used to hold the where clause of the join
DatabaseSchema Schema Owner schema for the relational tables
Name name  
DerivedType Datatype Datatype for Dimension Members
DataType   See datatype conversion array
Length Precision  
Name   Derived from the datatype
PhysicalName   Derived from the datatype
Scale Scale  
UserDefined   set to FALSE
DesignPackage   One default Package is created to store the tables and dimensions.
Name   Set to Logical View
UserDefined   Set to FALSE
Dimension Fact, Dimension  
Name Name  
Type Type set to FACT for the Fact, REGULAR for Dimensions and TIME for the Time Dimension
DimensionAttribute Member  
Description Description  
Hide DisplayFlag  
Name Name  
FeatureMap Join, Member Used to hold the traceability of Joins and Members
Description   Additional description, in case the expression is complex
Operation SQL Expression  
Hierarchy Hierarchy  
Description Description  
Name Name  
HierarchyLevelAssociation HierarchyMember  
Position LevelNumber  
Join Join  
Name   Computed
UserDefined   set to TRUE
JoinRole Join  
Level HierarchyMember  
Name Name  
LevelKey HierarchyMember  
Name Name  
Measure Member Numeric members that can be aggregated are imported as measures
DefaultAggregation AggregateType  
Hide DisplayFlag  
Name BusinessName  
PhysicalName Name  
StoreModel OLAP Model The model is built using the relational and dimensional defined in the XML file.
Description Description  
Name Name