Bridge Specifications
| Vendor | Oracle |
| Tool Name | Oracle Business Intelligence (OBI) Enterprise Edition (Server) |
| Tool Version | 10.1 to 12c |
| Tool Web Site | http://www.oracle.com/technetwork/middleware/bi-foundation/overview/index.html |
| Supported Methodology | [Business Intelligence] Multi-Model, Metadata Repository, BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Dimensional Source, Expression Parsing, Report Structure), Graphical Layout via Java API |
BRIDGE INFORMATION
Import tool: Oracle Oracle Business Intelligence (OBI) Enterprise Edition (Server) 10.1 to 12c (http://www.oracle.com/technetwork/middleware/bi-foundation/overview/index.html)
Import interface: [Business Intelligence] Multi-Model, Metadata Repository, BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Dimensional Source, Expression Parsing, Report Structure), Graphical Layout via Java API from Oracle Business Intelligence (OBI) Enterprise Edition (Server)
Import bridge: 'OracleBIEE' 10.1.0
BRIDGE DOCUMENTATION
This bridge imports from Oracle Business Intelligence Enterprise Edition (formerly Siebel Analytics).
This is a stitching bridge that calls Oracle Business Intelligence Answers import bridge to import Analysis(former Requests) and KPI reports,
and Oracle Business Intelligence Server import bridge to import OBIEE repository models.
Note: when importing OBIEE metadata from a large OBIA application, it is critical to adjust the bridge for memory optimization:
- Use a 64 bit JVM with increased memory to 4G
Update the file $MetaIntegration/conf/conf.properties with appropriate -Xmx parameter for a 64 bit JVM, for example:
M_JAVA_HOME=..\jre
M_JAVA_OPTIONS=-Xmx4G
The bridge Miscellaneous parameter can also be used to specify the amount of Java memory to allocate.
- Set the "Optimize for large models" bridge parameter to "True"
SUPPORT
Q: How do I provide metadata to the support team to reproduce an issue?
A: Provide the following files:
- The Oracle BI Administration tool natively stores metadata in a Repository RPD file, so you must supply a copy of that file. By default this file is located in \OracleBI\server\Repository. Provide this file along with the userID and password necessary to open it.
Alternative method: using Oracle BI Administration tool, connect to a live online repository.
From the File menu, select Copy As... and specify the name of the local RPD file where the repository copy will be stored.
Supply that file.
- For reports (in version 10.x they are called Requests, in version 11.x they are called Analyses), the metadata is contained inside OBIEE catalog. You may use OBIEE Catalog Manager tool as follows:
1. Go to File -> Open Catalog (either online or offline)
2. Offline mode, v10.x: point to OracleBIData/web/catalog/<MyCatalog> as the path.
Offline mode, v11.x: point to <instance>/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalog/<MyCatalog> as the path.
Check Read Only box for safety.
3. For online mode: type in OBI server URL that would look like http://OBIServer:9704/analytics/saw.dll (replace OBIServer with your OBI machine name).
Check Read Only box for safety.
4. Click OK
5. Select the root '/' folder in the tree
5. Go To File -> Archive to create the archive file
Provide the resulting archive file.
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | |||
| Version | Select the version of OBIEE server you want to import from. In Auto Detect mode, the bridge will attempt to read the version using the following URLs: For version 10.x: http://hostname:port/analytics/res/version.xml or http://hostname:port/analytics-ws/res/version.xml if an OBIEE server is configured and protected by OAM For version 11.x and 12.x: http://hostname:port/analytics/saw.dll?aboutPage or http://hostname:port/analytics-ws/saw.dll?aboutPage if an OBIEE server is configured and protected by OAM |
ENUMERATED |
|
Auto Detect | ||||
| Server URL | Enter the Presentation Server URL here For OBIEE deployed on Oracle Containers for Java (OC4J), the default port is 9704. (http://host:9704/analytics/saw.dll) For OBIEE deployed on Oracle WebLogic, the default port is 7001. (http://host:7001/analytics/saw.dll) For OBIEE deployed on Oracle HTTP Server (OHS), the default port is 7777. (http://host:7777/analytics/saw.dll) For OBIEE deployed on Microsoft's Internet Information Services (IIS), the default port is 80. (http://host:80/analytics/saw.dll) Accessing OBIEE via Oracle Access Manager (OAM): For an OBIEE server that is configured and protected by OAM, the Server URL may need to be entered as: http://host:port/analytics-ws/saw.dll The WebService WSDL descriptor file may be accessed like so: version 10g: http://host:port/analytics/saw.dll?WSDL version 11g: http://host:port/analytics/saw.dll/wsdl/v6 version 12c: http://host:port/analytics-ws/saw.dll/wsdl/v12 Accessing OBIEE via SSL/HTTPS: In order to connect to OBIEE presentation server over SSL link, the bridge needs to trust the server certificate. The best way to achieve this is to extract the root certificate used by the Oracle Weblogic Managed Servers (that are hosting the web services) into the local keystore of the the machine that runs MIMB. The procedure below outlines the necessary steps. 1. Confirm the location of the root certificate for OBIEE server. - Open the Weblogic console in a browser. By default, the location of the Weblogic console is: http://hostname:7001/console - From the Oracle WebLogic Server Administration Console, select SSL tab and go to the Identity area. By default, the Certificate location is from the Demo Identity Keystore. If this is the case, navigate to the Keystores tab and review the location of the Demo Identity Keystore. Note that the Demo Identity Keystore's default location is: <middleware_home>/wlserver_10.3_server/lib/DemoIdentity.jks Use Oracle Java keytool utility on the server to view and export the root certificate. 2. On the MIMB machine, using Java keytool, create a private keystore by importing the root certificate exported above. Let's say the certificate file name is CertGenCA.der, so the command would look like this: keytool -importcert -file CertGenCA.der -alias obiee11_certificate -keystore "${MODEL_BRIDGE_HOME}\jre\lib\security\obiee" -storepass "obieeobiee" When asked if you want to trust this certificate, confirm with 'yes'. A new keystore will be created under "${MODEL_BRIDGE_HOME}\jre\lib\security" and named obiee if it does not exist. You can import multiple certificates from different OBIEE servers into the same single keystore, just give each new certificate a unique alias. 3. Now the bridge should be able to connect to OBIEE server via SSL. |
STRING | http://localhost:9704/analytics/saw.dll | Mandatory | ||||
| Login User | Enter the username which the bridge will use to log in. Be sure this user name has necessary permissions to access the objects you wish to import. | STRING | Administrator | Mandatory | ||||
| Login Password | Enter the password associated with the username which the bridge will use to log in. | PASSWORD | ||||||
| File | The Oracle BI Administration tool natively stores metadata in a Repository RPD file. For version 11.x, convert the RPD file to XML format by performing the following steps: 1. run the bi-init.cmd (or bi-init.sh on UNIX) script to launch a command prompt (or shell) window that is initialized to your Oracle instance: ORACLE_INSTANCE\bifoundation\OracleBIApplication\coreapplication\setup\bi-init 2. use the 'biserverxmlgen' command line utility to generate XML: biserverxmlgen -R paint.rpd -P Admin123 -O paint.xml -N -Q -8 The bridge uses the generated XML file as input. Note: for version 11.x, the UDML file format is not supported by the bridge. For version 10.x, convert the RPD file to UDML format by performing the following: use the nQUDMLGen command line utility to generate a UDML file: $OracleBIHome$\server\Bin QUDMLGen.exe -U Administrator -P Administrator -R paint.rpd -O paint.udml -N -Q -8 The bridge uses the generated UDML file as input. |
FILE | *.* | Mandatory | ||||
| Variable values file | File defining list of RPD variable values in format: variable1_name=variable1_value variable3_name=variable2_value ... variableN_name=variableN_value RPD models may use variables to parameterize SQL statements. In many cases, the values which must be assigned to these variables are defined at runtime. In such cases, the bridge will report warning in the log that it could not determine the value of a variable and will simply leave that variable name without any substitution in the resulting model. In order to determine the correct substitution values for these variables, the bridge reads a variable value file with the variable names and the correct value to substitute. Place the pathname of a variable value file in this parameter. Variable names are case insensitive and trimmed of all leading and trailing spaces. |
FILE | *.* | |||||
| Repository subset | This option is used to subset the amount of reports retrieved from the OBI Presentation Server. Specify here a semicolon separated list of objects path, the bridge will import the selected folders and reports. - the root folder path is: / - the shared folder path is: /shared - the administrator user folder is: /users/administrator |
REPOSITORY_SUBSET | / | Mandatory | ||||
| Optimize for large models | Specify whether or not to optimize the import for large OBI repository models. 'True' - ignore foreign keys, joins, relationships, logical foreign keys during import. Also, do not store expression tree objects along with lineage links. Ignoring such objects will result in a smaller model, and require less memory at runtime. This mode is recommended for large UDML or XML input files. This is the default value. 'False' - the entire repository model will be imported. In this mode, more memory is required at runtime. This mode is recommended for small to medium UDML or XML input files. |
BOOLEAN |
|
True | ||||
| Incremental import | Specifies whether to import only the changes made in the source or to re-import everything (as specified in other parameters). True - import only the changes made in the source. False - import everything (as specified in other parameters). An internal cache is maintained for each metadata source, which contains previously imported models. If this is the first import or if the internal cache has been deleted or corrupted, the bridge will behave as if this parameter is set to 'False'. |
BOOLEAN |
|
True | ||||
| Multiple threads | Number of worker threads to harvest metadata asynchronously. Leave the parameter blank to have the bridge compute the value, between 1 and 6, based on JVM architecture and number of available CPU cores. Specify a numeric value greater or equal to 1 to provide the actual number of threads. If the value specified is invalid, a warning will be issued and 1 will be used instead. If you experience out of memory conditions when harvesting metadata asynchronously, experiment with smaller numbers. If your machine has a lot of available memory (e.g. 10 Gb or more), you can try larger numbers when harvesting many documents at once. Note that setting the number too high can actually decrease the performance due to resource contention. |
NUMERIC | ||||||
| Miscellaneous | Specify miscellaneous options identified with a -letter and value. For example, -m 4G -v set environment variable(s) (e.g. -v var1=value -v var2="value with spaces"). -m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ). -j the last option that is followed by Java command line options (e.g. -j -Dname=value -Xms1G). -r to remove the report pages and their graphical structure. |
STRING |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"Oracle Business Intelligence (OBI) Enterprise Edition (Server)" Metamodel Oracle Business Intelligence (Web Catalog) |
Mapping Comments |
| DirectoryStructureModel | Catalog | contents of the OBIEE catalog |
| CreationTime | Creation Time | |
| Description | Description | |
| ImportDate | Import Date | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| Folder | Dashboard, Folder, Dashboard Page | |
| Author | Author | |
| CreationTime | Creation Time | |
| Description | Description | |
| LastModificationTime | Last Modification Time | |
| Modifier | Modifier | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| StoreContent | Answers Report, KPI, Connection, RPD Content | Represents objects in OBIEE catalog |
| Author | Author | |
| CreationTime | Creation Time | |
| Description | Description | |
| LastModificationTime | Last Modification Time | |
| Modifier | Modifier | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type |
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"Oracle Business Intelligence (OBI) Enterprise Edition (Server)" Metamodel Oracle Business Intelligence (Connection) |
Mapping Comments |
| Attribute | Column | |
| Comment | Comment | |
| Description | Definition | |
| DesignLevel | Design Level | |
| ExtraConstraint | Constraint | |
| InitialValue | Initial Value | |
| Name | Name | |
| NativeId | Native Id | |
| Optional | Nullable | |
| PhysicalName | Physical Name | |
| Position | Position | |
| Class | Table | physical table in the database |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| DatabaseSchema | Database Schema | |
| Description | Description | |
| Name | Name | |
| NativeId | Native Id | |
| NativeType | Native Type | |
| StoreModel | Connection Model | |
| Name | Name | |
| StoreType | Store Type | |
| SystemMajorVersion | System Major Version | |
| SystemMinorVersion | System Minor Version | |
| SystemReleaseVersion | System Release Version | |
| SystemType | System Type |