Note:
AWS
Bridge Specifications
| Vendor | Oracle |
| Tool Name | Oracle Business Intelligence (OBI) Answers, KPI and Prompt Reports (XML file) |
| Tool Version | 10.1 to 12c |
| Tool Web Site | http://www.oracle.com/technetwork/middleware/bi-foundation/overview/index.html |
| Supported Methodology | [Business Intelligence] BI Report (Dimensional Source, Expression Parsing, Report Structure) via XML File |
| Data Profiling |  |
| Incremental Harvesting | |
| Multi-Model Harvesting | |
| Remote Repository Browsing for Model Selection | |
SPECIFICATIONS
Tool: Oracle / Oracle Business Intelligence (OBI) Answers, KPI and Prompt Reports (XML file) version 10.1 to 12c via XML File
See http://www.oracle.com/technetwork/middleware/bi-foundation/overview/index.html
Metadata: [Business Intelligence] BI Report (Dimensional Source, Expression Parsing, Report Structure)
Component: OracleBIAnswers version 11.2.0
OVERVIEW
Imports an Oracle Business Intelligence Answers (formerly Siebel Analytics Web) report.
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 troubleshooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope |
| File | Specify Oracle BI Answers request (v10.x) or analysis (v11.x) XML file to import. The XML file may be obtained via OBIEE web-based user interface: OBIEE 10.x: 1. Connect, via a web browser, to the OBIEE Answers instance (e.g. http://localhost:9704/analytics/saw.dll?Answers). 2. Login when prompted (e.g. Administrator/Administrator). 3. On the left side of the page, click on Catalog tab and navigate to the folder of interest. 4. Select a request of interest (e.g. 'Customer Details.'). 5. After the request opens, on the right pane select Modify and then Advanced. 6. In the 'Request XML' text field, one may see the XML contents. 7. Select the XML contents, copy it to clipboard and paste into a new empty file using any text editor. 8. Save the file under any name with .XML extension. 9. Feed the resulting XML file as an input to the bridge. OBIEE 11.x: 1. Connect, via a web browser, to the OBIEE Answers instance (e.g. http://localhost:9704/analytics). 2. Login when prompted (e.g. weblogic/weblogic). 3. On the left side of the page, under 'Browse/Manage...' go to 'All Content' drop down list and select 'Browse Oracle BI Presentation Catalog'. (As an alternative, on the right side of the page, in the second horizontal menu, select 'Catalog'). 4. On the left side of the page, navigate to the folder of interest. 5. On the right side of the page, find the analysis of interest and select 'Edit' under its name. 6. After the analysis has opened, select 'Advanced' tab and go to 'Analysis XML' text field. 7. Copy the entire contents of the 'Analysis XML' text field into clipboard and paste into a new empty file using any text editor. 8. Save the file under any name with .XML extension. 9. Feed the resulting XML file as an input to the bridge. |
FILE | *.* | Mandatory | |
| Report name | Type the name of the reporting model. Answers XML files do not contain the report name. If you do not type a name, the file name is used as the report name. For KPI reports this parameter is ignored, the report name is specified in the report itself. | STRING | |||
| Miscellaneous | INTRODUCTION Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g. -connection.cast MyDatabase1="MICROSOFT SQL SERVER" Some options can be used multiple times if applicable, e.g. -connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2; As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g. ETL/Miscellaneous.txt JAVA ENVIRONMENT OPTIONS -java.memory <Java Memory's maximum size> (previously -m) 1G by default on 64bits JRE or as set in conf/conf.properties, e.g. -java.memory 8G -java.memory 8000M -java.parameters <Java Runtime Environment command line options> (previously -j) This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g. -java.parameters -Dname=value -Xms1G The following option must be set when a proxy is used to access internet (this is critical to access https://repo.maven.apache.org/maven2/ and exceptionally a few other tool sites) in order to download the necessary third-party software libraries. Note: The majority of proxies are concerned with encrypting (HTTPS) the outside (of the company) traffic and trust the inside traffic that can access proxy over HTTP. In this case, an HTTPS request reaches the proxy over HTTP where the proxy HTTPS-encrypts it. -java.parameters -java.parameters -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass MODEL IMPORT OPTIONS -model.name <model name> Override the model name, e.g. -model.name "My Model Name" -prescript <script name> This option allows running a script before the bridge execution. The script must be located in the bin directory (or as specified with M_SCRIPT_PATH in conf/conf.properties), and have .bat or .sh extension. The script path must not include any parent directory symbol (..). The script should return exit code 0 to indicate success, or another value to indicate failure. For example: -prescript "script.bat arg1 arg2" -postscript <script name> This option allows running a script after successful execution of the bridge. The script must be located in the bin directory (or as specified with M_SCRIPT_PATH in conf/conf.properties), and have .bat or .sh extension. The script path must not include any parent directory symbol (..). The script should return exit code 0 to indicate success, or another value to indicate failure. For example: -postscript "script.bat arg1 arg2" -cache.clear Clears the cache before the import, and therefore will run a full import without incremental harvesting. If the model was not changed and the -cache.clear parameter is not used (incremental harvesting), then a new version will not be created. If the model was not changed and the -cache.clear parameter is set (full source import instead of incremental), then a new version will be created. -backup <directory> This option allows to save the bridge input metadata for further troubleshooting. The provided <directory> must be empty. The primary use of this option is for data store import bridges, in particular JDBC based database import bridges. Note that this option is not operational on some bridges including: - File based import bridges (as such input files can be used instead) - DI/BI repository import bridges (as the tool's repository native backup can be used instead) - Some API based import bridges (e.g. COM based) for technical reasons. DATA CONNECTION OPTIONS Data Connections are produced by the import bridges typically from ETL/DI and BI tools to refer to the source and target data stores they use. These data connections are then used by metadata management tools to connect them (metadata stitching) to their actual data stores (e.g. databases, file system, etc.) in order to produce the full end to end data flow lineage and impact analysis. The name of each data connection is unique by import model. The data connection names used within DI/BI design tools are used when possible, otherwise connection names are generated to be short but meaningful such as the database / schema name, the file system path, or Uniform Resource Identifier (URI). The following option allows to manipulate connections. These options replaces the legacy options -c, -cd, and -cs. -connection.cast ConnectionName=ConnectionType Casts a generic database connection (e.g. ODBC/JDBC) to a precise database type (e.g. ORACLE) for SQL Parsing, e.g. -connection.cast "My Database"="MICROSOFT SQL SERVER". The list of supported data store connection types includes: ACCESS APACHE CASSANDRA DB2/UDB DENODO GOOGLE BIGQUERY HIVE MYSQL NETEZZA ORACLE POSTGRESQL PRESTO REDSHIFT SALESFORCE SAP HANA SNOWFLAKE MICROSOFT SQL AZURE MICROSOFT SQL SERVER SYBASE SQL SERVER SYBASE AS ENTERPRISE TERADATA VECTORWISE HP VERTICA -connection.rename OldConnection=NewConnection Renames an existing connection to a new name, e.g. -connection.rename OldConnectionName=NewConnectionName Multiple existing database connections can be renamed and merged into one new database connection, e.g. -connection.rename MySchema1=MyDatabase -connection.rename MySchema2=MyDatabase -connection.split oldConnection.Schema1=newConnection Splits a database connection into one or multiple database connections. A single database connection can be split into one connection per schema, e.g. -connection.split MyDatabase All database connections can be split into one connection per schema, e.g. -connection.split * A database connection can be explicitly split creating a new database connection by appending a schema name to a database, e.g. -connection.split MyDatabase.schema1=MySchema1 -connection.map SourcePath=DestinationPath Maps a source path to destination path. This is useful for file system connections when different paths points to the same object (directory or file). On Hadoop, a process can write into a CSV file specified with the HDFS full path, but another process reads from a Hive table implemented (external) by the same file specified using a relative path with default file name and extension, e.g. -connection.map /user1/folder=hdfs://host:8020/users/user1/folder/file.csv On Linux, a given directory (or file) like /data can be referred to by multiple symbolic links like /users/john and /users/paul, e.g. -connection.map /data=/users/John -connection.map /data=/users/paul On Windows, a given directory like C:\data can be referred to by multiple network drives like M: and N:, e.g. -connection.map C:\data=M:\ -connection.map C:\data=N:\ -connection.casesensitive ConnectionName Overrides the default case insensitive matching rules for the object identifiers inside the specified connection, provided the detected type of the data store by itself supports this configuration (e.g. Microsoft SQL Server, MySql etc.), e.g. -connection.casesensitive "My Database" -connection.level AggregationLevel Specifies the aggregation level for the external connections, e.g.-connection.level catalog The list of the supported values: server catalog schema (default) ORACLE BUSINESS INTELLIGENCE ANSWERS, KPI AND PROMPT REPORTS OPTIONS -r Remove the report pages and their graphical structure. bp_miscellaneous_default: "" |
STRING |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"Oracle Business Intelligence (OBI) Answers, KPI and Prompt Reports (XML file)" Metamodel Oracle Business Intelligence (KPI) |
Mapping Comments |
| Condition | Condition | Report filter |
| Description | Description | |
| Hide | Hide | |
| InitialValue | Initial Value | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Optional | Optional | |
| PhysicalName | Physical Name | |
| Position | Position | |
| ConnectionClassifier | Server Variables | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| ConnectionFeature | Server Session Variable, Server Repository Variable | |
| Name | Name | |
| NativeType | Native Type | |
| ConnectionPackage | Owner, Subject Area | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| DataAttribute | Presentation Variable, Dynamic Variable, Criteria Hierarchical Column, Repository Variable, Criteria Column, Session Variable | |
| Description | Description | |
| InitialValue | Initial Value | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Optional | Optional | |
| PhysicalName | Physical Name | |
| Position | Position | |
| Usage | Usage | |
| DataSet | Presentation Variables, Repository Variables, Criteria, Session Variables | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| Dimension | Extended Subject Area, Presentation Table | |
| Description | Description | |
| Hide | Hide | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Type | Type | |
| DimensionAttribute | Extended Subject Area Column, Presentation Column | Represents presentation column inside presentation table |
| Description | Description | |
| Hide | Hide | |
| InitialValue | Initial Value | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Optional | Optional | |
| OriginalName | Original Name | |
| Position | Position | |
| Sort | Sort | |
| Hierarchy | Presentation Hierarchy | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| Type | Type | |
| Level | Presentation Level | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Report | Report | |
| Description | Description | |
| Name | Name | The report name can be retrieved from the presentation server if the bridge runs via the Oracle BI EE repository bridge, or computed from file name otherwise |
| NativeId | Native Id | |
| NativeType | Native Type | |
| ReportField | Report Field | Represents the usage and display of a query column on a View |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| ReportPage | Page | A single page is created, for the purpose of holding all possible views |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| StoreConnection | Variables, Extended Subject Areas, Presentation | For reports, represents RPD presentation layer |
| Connection | Connection | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| StoreType | Store Type | |
| SystemMajorVersion | System Major Version | |
| SystemMinorVersion | System Minor Version | |
| SystemReleaseVersion | System Release Version | |
| SystemType | System Type | |
| SystemTypeOld | System Type Old | |
| StoreModel | KPI | |
| Author | Author | |
| CreationTime | Creation Time | |
| Description | Description | |
| ModificationTime | Modification Time | |
| Modifier | Modifier | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| StoreType | Store Type | |
| SystemMajorVersion | System Major Version | |
| SystemMinorVersion | System Minor Version | |
| SystemReleaseVersion | System Release Version | |
| SystemType | System Type | |
| SystemTypeOld | System Type Old |
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"Oracle Business Intelligence (OBI) Answers, KPI and Prompt Reports (XML file)" Metamodel Oracle Business Intelligence (Answers Report) |
Mapping Comments |
| Condition | Condition | Report filter |
| Description | Description | |
| Hide | Hide | |
| InitialValue | Initial Value | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Optional | Optional | |
| PhysicalName | Physical Name | |
| Position | Position | |
| ConnectionClassifier | Server Variables | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| ConnectionFeature | Server Session Variable, Server Repository Variable | |
| Name | Name | |
| NativeType | Native Type | |
| ConnectionPackage | Owner, Subject Area | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| DataAttribute | Presentation Variable, Dynamic Variable, Criteria Hierarchical Column, Repository Variable, Criteria Column, Session Variable | |
| Description | Description | |
| InitialValue | Initial Value | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Optional | Optional | |
| PhysicalName | Physical Name | |
| Position | Position | |
| Usage | Usage | |
| DataSet | Presentation Variables, Repository Variables, Criteria, Session Variables | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| Dimension | Extended Subject Area, Presentation Table | |
| Description | Description | |
| Hide | Hide | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Type | Type | |
| DimensionAttribute | Extended Subject Area Column, Presentation Column | Represents presentation column inside presentation table |
| Description | Description | |
| Hide | Hide | |
| InitialValue | Initial Value | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Optional | Optional | |
| OriginalName | Original Name | |
| Position | Position | |
| Sort | Sort | |
| Hierarchy | Presentation Hierarchy | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| Type | Type | |
| Level | Presentation Level | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Report | Report | |
| Description | Description | |
| Name | Name | The report name can be retrieved from the presentation server if the bridge runs via the Oracle BI EE repository bridge, or computed from file name otherwise |
| NativeId | Native Id | |
| NativeType | Native Type | |
| ReportAxis | Axis | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| Role | Role | |
| ReportChart | Funnel, Graph Chart, Chart, Gauge | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| ReportField | Report Field | Represents the usage and display of a query column on a View |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| ReportMatrix | Pivot Table | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| ReportPage | Page | A single page is created, for the purpose of holding all possible views |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| ReportRectangle | Narrative View, Column Selector, Title View, Ticker, View Selector, Compound View, Filters View | For other views, like Title view, Narrative view, View Selector, filters view, compound view |
| Description | Description | |
| Name | Name | inferred from the view id |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| ReportTable | Table View | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| ReportText | Text, Html View | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Position | Position | |
| Value | Value | |
| StoreConnection | Variables, Extended Subject Areas, Presentation | For reports, represents RPD presentation layer |
| Connection | Connection | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| StoreType | Store Type | |
| SystemMajorVersion | System Major Version | |
| SystemMinorVersion | System Minor Version | |
| SystemReleaseVersion | System Release Version | |
| SystemType | System Type | |
| SystemTypeOld | System Type Old | |
| StoreModel | Answers Report | |
| Author | Author | |
| CreationTime | Creation Time | |
| Description | Description | |
| ModificationTime | Modification Time | |
| Modifier | Modifier | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| PhysicalName | Physical Name | |
| StoreType | Store Type | |
| SystemMajorVersion | System Major Version | |
| SystemMinorVersion | System Minor Version | |
| SystemReleaseVersion | System Release Version | |
| SystemType | System Type | |
| SystemTypeOld | System Type Old |