3 Data Lineage Extensibility

This chapter explains how to set up the Data Lineage Dashboard to work with customized reports or BI metadata RPD files:

Refresh the RPD Lineage Metadata

If the OHF SSA RPD files has been extended, follow the instructions below to refresh the RPD lineage metadata:

  1. Open the extended RPD file in the Oracle BI Administration Tool.

  2. Go to Tools and select Utilities.

  3. Select Repository Documentation and click Execute.

    Figure 3-1 Utilities Window

    Surrounding text describes Figure 3-1 .
  4. Navigate to a directory where you want to save the repository metadata.

  5. In the Save as type: selection box, choose Tab Separated Values (*.txt).

  6. Enter a name for the file and click Save.

    Figure 3-2 Saving the RPD Data Lineage

    Saving the RPD metadata
  7. After the export completes, change the file's extension from .txt to .tsv.

  8. Open SQL Developer.

  9. Connect to the OHF Exterprise Schema where the OHF_RPD_LINEAGE table is installed.

  10. Expand the Tables Section.

  11. Right click on the OHF_RPD_LINEAGE table and select Import Data.

  12. In the file browser, navigate to the location where you exported the RPD metadata file.

  13. Choose the *.tsv file type and select the exported RPD metadata file.

  14. Click Open.

  15. When prompted to Import Data Record Terminator, click OK.

  16. When prompted to Import Data Field Format, click OK.

  17. In the Data Preview screen of the Data Import Wizard, set the Left Enclosure to none.

    Figure 3-3 Data Preview

    Data Preview
  18. In the Import Data Field Format screen, click OK.

  19. Click Next.

  20. In the Import Method screen, click Next.

  21. In the Selected Columns panel, make sure all columns are listed and click Next.

  22. In the Column Definition screen, map all the source data columns to the target table columns. The source and target columns have similar names and can be matched either by name or by order.

    Figure 3-4 Column Definition

    Column Definition
  23. After you map all the columns, click Next.

  24. Clisk Finish.

  25. A data import progress screen is displayed.

  26. After the import is complete, a success message is displayed. Click OK.

  27. Query the OHF_RPD_LINEAGE table to retrieve the record count and compare it with the row count in the RPD Metadata file:

    Select count(*) from OHF_RPD_LINEAGE;

Refresh the Catalog Lineage Metadata

If the OHF SSA Dashboards have been extended, follow the instructions below to refresh the RPD lineage metadata:

  1. Open the Command Prompt.

  2. Navigate to the to bi\bitools\bin subdirectory in the Oracle BI Client Tool installation directory. For example:

    cd C:\Install\middleware\BI_Home\bi\bitools\bin

  3. Create a .txt file with the WebLogic credentials in the following format:

    login=<username>
    pwd=<password>

  4. Execute the following command:

    runcat.cmd -cmd report -online <BI Analytics URL where the dashboard catalog contents reside> -credentials <Path to the credentials file containing the weblogic user name and password> -outputFile <Path to the output file with extension .csv where the catalog metadata contents have to be stored> -folder <Location of the OBI Catalog Folder> -delimiter "|~" -type "Analysis" -fields "Owner:Folder:Name:Path:Subject Area:Table:Column:Formula"

    For example:

    runcat.cmd -cmd report -online http://obixxx.mycompany.com:9504/analytics/saw.dll? -credentials D:/login.txt -outputFile D:/ohf_hcd_catalog.csv -folder "/shared/Oracle Healthcare Foundation" -delimiter "|~" -type "Analysis" -fields "Owner:Folder:Name:Path:Subject Area:Table:Column:Formula"

  5. After completion, a success message is displayed:

    Making SOAP connection to http://obixxx.mycompany.com:9504/analytics/saw.dll?
    Running Report..4..3..2..1..0..Done!

  6. Open SQL Developer.

  7. Connect to the OHF Enterprise Schema where the OHF_CATALOG_LINEAGE table is installed.

  8. Expand the Tables section.

  9. Right click on the OHF_CATALOG_LINEAGE table and select Import Data.

  10. In the File browser, navigate to the location where the Catalog Metadata File is saved.

  11. Choose the .csv file type and select the Catalog Metadata file.

  12. Click Open.

  13. When prompted to Import Data Record Terminator, click OK.

  14. When prompted to Import Data Field Format, click OK.

  15. In the Data Import Wizard, select the delimited format.

  16. Set the Delimiter to |~.

  17. Set the Left Enclosure to none.

    Figure 3-5 Data Preview

    Data Preview
  18. When prompted to Import Data Field Format, click OK.

  19. Click Next.

  20. In the Import Method screen, click Next.

  21. In the Selected Columns pane, make sure all columns are listed and click Next.

  22. In the Column Definition screen, map all the source data columns to the target table columns. The source and target columns have similar names and can be matched either by name or by order.

    Figure 3-6 Column Definition

    Column Definition
  23. After you map all the columns, click Next.

  24. Click Finish.

  25. A data import progress screen is displayed.

  26. After the import is complete, a success message is displayed. Click OK.

  27. Query the OHF_CATALOG_LINEAGE table to retrieve the record count and compare it with the row count in the Catalog Metadata file:

    Select count(*) from OHF_CATALOG_LINEAGE;

Refresh the OBIEE Dashboards

To view the updated data lineage information in the Data Lineage Dashboard, purge the OBIEE cache by following the instructions below:

  1. Log in to the Oracle BI Analytics page. For example: http://obixxx.mycompany.com:9704/analytics

  2. Go to Administration.

  3. In the Session Management section, select Manage Sessions.

  4. Click Close All Cursors.

  5. Go to Administration.

  6. In the Maintenance and Troubleshooting section, select Issue SQL.

  7. In the Issue SQL screen, type the following command in the text box:

    Call sapurgeallcache()

  8. Click Issue SQL.

  9. After purging the cache, the following success message is displayed.

    [59118] Operation SAPurgeAllCache succeeded!

Now, the custom reports will be visible in the Data Lineage Dashboard.