Configuring the Scripts Automating the Lineage Tasks

17 The JDBC Driver to connect to the ODI Master Repository ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver The Database user for the schema that contains the ODI master repository. ODI_MASTER_USER=MASTER_REPO This user’s password ODI_MASTER_PASS=master_password The ODI user with SUPERVISOR privileges ODI_SUPERVISOR_USER=SUPERVISOR The ODI Password of the ODI User with SUPERVISOR privileges ODI_SUPERVISOR_PASS=supervisor password Work Repository containing the lineage ODI_SECU_WORK_REP=WORK_REP1 The Web Catalog folder to export in the report. Eg: sharedODI OBIEE_WEBCAT_FOLDER_TO_EXPORT=sharedODI Option to deploy ODI Artifacts on the BI Server. INSTALL_ODI_LINEAGE=no Option to export BI Metadata as flat files EXPORT_OBIEE_METADATA=yes Encoding Passwords To avoid storing the passwords in plain text, use the encode.[sh|bat] password command to encode and store the passwords in the property file. If the password are encoded, the property names will change to ODI_MASTER_REPO_ ENCODED_PASS, ODI_SUPERVISOR_ENCODED_PASS, and OBIEE_RPD_ ENCODED_PASS.

19.5.2 Automating Lineage Deployment

The install lineage script deploys the following ODI Artifacts in the OBIEE Server: ■ Lineage RPD ■ Lineage Web Catalog 11g OBIEE only The script uses the OBIEE tools to merge the Lineage RPD and Lineage Web Catalog with the BIEE Server components. Syntax The script syntax is as follows: installlineage.bat [-propertyFile=property_file] [-prop_name=prop_value [...]] [-usage] where: ■ propertyfile represents the Property File that contains all the required properties to install the lineage artifacts. See Section 19.5.1, Configuring the Scripts for more information. If no value is specified, the User Wizard will be launched to gather the required information from the User. All the properties in Note: After running this script, you have to perform the tasks described in Section 19.2.4, Post-Installation Tasks . 18 Product TitleBookTitle as a Variable the property file can be overridden by specifying the property value in the command line option -propName=propValue. ■ prop_name represents the property that can be specified. The value specified in prop_value will override the value specified in the property file if any. ■ prop_value represents the value for the prop_name property. It will override the value specified in the property file if any. ■ usage prints the detailed usage information

19.5.3 Automating Lineage Refresh

The refresh lineage script performs one of the following operations, depending on the value set in the EXPORT_OBIEE_METADATA option defined in the property file: ■ Export and refresh metadata, if the EXPORT_OBIEE_METADATA option is set to Yes ■ Refresh lineage metadata, if the EXPORT_OBIEE_METADATA option is set to No Note that in order to use refreshlineage.sh you need to manually copy the repo_doc.text and the webcat_doc.txt files to the target Linux machine. Syntax The script syntax is as follows: refreshlineage [-propertyFile=property_file] [-mappingFile=mapping_file] [-prop_ name=prop_value [...]] [-usage] where: ■ propertyfile represents the Property File that contains all the required properties to export and consolidate lineage metadata. See Section 19.5.1, Configuring the Scripts for more information. If no value is specified, the User Wizard will be launched to gather the required information from the User. All the properties in the property file can be overridden by specifying the property value in the command line option -prop_name=prop_value. ■ mappingfile represents the mapping of the Model code to BI_PHYSICAL_DB, BI_PHYSICAL_SCHEMA and BI_PHYSICAL_CATALOG. This mapping must be provided in the form of a comma separated values .csv file. Example 19–2 shows a sample mapping file. Example 19–2 Mapping File c Copyright Oracle. All rights reserved. Sample Mapping File for ODI-OBIEE Metadata Lineage Format: BI Physical DB, BI Physical Schema, BI Physical Catalog, ODI Model ID Note: Lines starting with are considered as comments. DB-1,Schema-1,Catalog-1,model1 DB-2,Schema-2,Catalog-2,model2 Note: If the propertyFile and mappingFile options are not specified, the UI wizard will be shown to take user input. Otherwise the script will be run from command line itself taking the values from the property file and mapping file to refresh lineage and the UI wizard will not be shown. 19

19.6 Using the Lineage in OBIEE Dashboards

The OBIEE Lineage Artifact deployed in the BIEE Server allow for many usage scenarios. The most common usage scenarios are listed in this section: ■ Viewing Execution Statistics ■ Viewing and Filtering Lineage Data ■ Using the Dashboard ■ Using Lineage and Hierarchy ■ Using Contextual Lineage

19.6.1 Viewing Execution Statistics

In this scenario, we want to display the execution statistics of ODI within a OBI-EE dashboard. To add ODI statistics, insert the RuntimeStats request from the Lineage Web Catalog into your dashboard. The statistics appear as shown in Figure 19–2 . Figure 19–2 Runtime Statistics This image shows the runtime statistics.

19.6.2 Viewing and Filtering Lineage Data

In this scenario, you want to view the lineage data and filter the results. To create such a dashboard, add the Prompt Lineage dashboard prompt and the LineageRequestColumns request on a dashboard. Both objects are in the lineage web catalog as shown in Figure 19–3 .