OBIEE Resource Configuration
Source System Properties
This configuration can be setup by creating a new connection on Admin UI > Connections tab or editing an existing connection in Admin UI > Connections > Reporting & BI > OBIEE > specific connection. New connection can also be created via Manta Orchestration API General Walkthrough Example.
One IBM Manta Data Lineage connection for OBIEE corresponds to one OBIEE server and its presentation catalog. The reports, data models, analyses, and dashboards that are stored in the presentation catalog will be analyzed.
This automatic extraction requires a connection using OBIEE Web Services, and the OBIEE server needs to be running.
Common Source System Properties
Property name |
Description |
Example |
---|---|---|
obiee.extractor.server |
Name of a resource representing this OBIEE server also known as the dictionary ID, used as an output subdirectory name for extracted definition files for reports and other objects |
Obiee1 |
obiee.extractor.address |
The complete URL address of the OBIEE server |
|
obiee.extractor.user |
User name for connection to the OBIEE server |
weblogic |
obiee.extractor.password |
User password for connection to the OBIEE server |
welcome1 |
obiee.extractor.include |
A regular expression for full object names to be extracted in the format |
/shared/SomeFolder |
obiee.extractor.exclude |
A regular expression for full object names NOT to be extracted in the format |
/shared/SomeFolder |
obiee.input.encoding |
Encoding of the provided OBIEE files; only necessary if an input has been served manually by the client. See Encodings for applicable values. |
UTF-8 |
Common Scanner Properties
This configuration is common for all OBIEE source systems and for all OBIEE scenarios, and is configure in Admin UI > Configuration > CLI > OBIEE > OBIEE Common. It can be overridden on individual connection level.
Property name |
Description |
Example (default value) |
---|---|---|
obiee.input.dir |
Directory with files automatically extracted from the OBIEE Presentation Catalog If analysis files are provided, they must contain the extension
|
${manta.dir.temp}/obiee/${obiee.extractor.server} |
obiee.manualInput.dir |
Directory for manually extracted OBIEE files, meaning both the repository dump and the Catalog Manager export |
${manta.dir.input}/obiee/${obiee.extractor.server} |
obiee.odbc.connection.definition.file |
Path to the optional ODBC connection definition file |
${manta.dir.input}/obiee/${obiee.extractor.server}/odbcConnectionDefinition.ini |
obiee.odbc.connection.definition.encoding |
Encoding of the ODBC connection definition file. See Encodings for applicable values. |
UTF-8 |
ODBC Connection Definition Settings
The connection settings for OBIEE are automatically exported by Manta Data Lineage during lineage analysis. But to resolve the ODBC connector, Manta Data Lineage needs more information about the source/destination system. The settings can be configured manually as follows.
-
Create or open the file referenced by the
obiee.odbc.connection.definition.file
property (e.g.,<MANTA_DIR_HOME>/input/obiee/${obiee.extractor.server}/odbcConnectionDefinition.ini
). -
Fill in each connection as much as possible. If you don't know how to fill in a property, leave it empty or don't even add it to the configuration file.
-
Add a new section for each connection shortcut; for example:
-
[
Shortcut_Name
] — the data source used in the ODBC connector -
Type=Oracle
— a type of system such as:-
Oracle
-
Teradata
-
MS SQL
-
Sybase
-
Netezza
-
Db2
-
JDBC
-
ODBC
-
FTP
-
Etc.
-
-
Connection_String=orcl
— It can be a JDBC connection string or any database identification such as the SID or host name. It can match theConnection_Id
in the manual dictionary mapping. -
Server_Name=Server
— the value depends on the type of system-
Microsoft SQL Server, Sybase, Teradata, Db2, and Netezza — the name of the server
-
Oracle and other databases — this value is ignored
-
FTP — host name
-
-
Database_Name=ORCL11
— the value depends on the type of system-
Oracle — global database name
-
Teradata, Microsoft SQL Server, Sybase, Db2, Netezza, and other databases — name of the default database
-
-
Schema_Name=Default
— the value depends on the type of system-
Teradata — this value is ignored
-
Microsoft SQL Server, Sybase, Oracle, Db2, Netezza, and other databases — name of the default schema
-
-
User_Name=user
— user name that logs in to the database (helps map the default database or schema; can be ignored)
-
-
Add a new line at the end of the parameters for each section.
Example of a section in the configuration file:
[Medical] [DB-HR] |
---|