p.20 Pts Odi11g Lineage Obiee

Embed Size (px)

Citation preview

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    1/23

    Copyright 2010, Oracle. All rights reserved.

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    2/23

    Oracle Data Integrator Data Lineage with OBIEE

    PTS Workshop: ODI 11g

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    3/23

    3

    OBIEE LineageLineage Drill Down vs. Hierarchy

    The Lineage icon allows you to drill down into a column lineage. The lineage goes down the following path:> The OBIEE Presentation Column(s) used in a request's column

    > The OBIEE Logical Column(s) used in a Presentation Column> The OBIEE Physical Column(s) used in a Presentation Column

    > The ODI Column(s) corresponding to OBIEE Physical Column(s)> The ODI source columns used to load a given ODI target column via an ODI interface. This path can

    recurse if the source columns

    One lineage level displayed in the dashboard

    Hierarchical column lineage

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    4/23

    4

    OBIEE LineageContextual Lineage

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    5/23

    Copyright 2010, Oracle. All rights reserved.

    OBIEE Lineage Components

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    6/23

    6

    2. Lineage Artifacts for OBIEE : Pre-packagedOBIEE artifacts are deployed in OBIEE toaccess the lineage information:

    Lineage RPD Lineage Web Catalog Requests Images used in these dashboards

    IntroductionOBIEE Lineage Components

    3. Command Line Tools and a Wizard to automate the lineage tasks: Deployment of the Lineage Artifacts for OBIEE in an OBIEE instance Extraction of the OBIEE Metadata from a OBIEE Instance Consolidation of the OBIEE and ODI Metadata in the ODI repository

    1. Lineage Tables Consolidate both the OBIEE and ODI

    metadata Stored in the ODI repository schema

    Contains the Physical,Logical and Presentationlayers to access theLineage Tables

    Used in existingdashboard tocreate report -to-source dashboards

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    7/237

    IntroductionLineage Lifecycle

    1. OBIEE Metadata Export : BIEE metadata (RPD and Web catalogs) is exported

    in file format into a temporary directory2. Metadata Consolidation : BIEE export files are consolidated with the ODI

    metadata (using an ODI Package) in the lineage tables

    3. Lineage Browsing : The lineage tables are accessed from the end- usersdashboard through the Lineage Artifacts that are depoyed in the BIEE Server

    Contains the

    consolidation processand is used to run it Contains all the

    Extract-Transform-Load (ETL)processes that loadthe data warehouse

    Hosts the lineagetables

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    8/23

    8

    OBIEE Lineage WizardProcess Overview

    refreshlineage.bat

    Propertiesfile

    Wizard screens Execute Action: Install Lineage Export Metadata & Refresh Lineage Refresh Lineage

    Command lineinstalllineage.batrefreshlineage.bat/.sh

    edit manually

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    9/23

    9

    Installing LineageOverview

    Installing Lineage in an OBIEE Server deploys therequired OBIEE artifacts in the OBIEE Repositoryand Web Catalog

    Setting up the Lineage process is required once.

    Use the OBIEE Lineage Wizard for installationNote : This wizard is also used for configuring and refreshing

    the Lineage.

    Post-installation tasks depend on OBIEE version

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    10/23

    10

    Installing LineageInstall Flow

    When Using OBIEE 10 g When Using OBIEE 11 gOBIEE Lineage wizard installs only theLineage RPD, not the Lineage Web CatalogRequests and the dashboard images

    OBIEE Lineage wizard installs only theLineage RPD and the Web CatalogRequests, not the and the dashboardimages

    1. Review the Requirements

    2. Install and Start the OBIEE Lineage Wizard(alternative : install lineage script)

    Wizard

    3. Use the OBIEE Lineage wizard to install Lineage in OBIEE Server anddeploy the OBIEE Lineage artifacts

    Wizard

    4. Deploy the Web Catalog requests in

    the OBIEE 10 g Web Catalog

    Done by the wizard For 10 g : Post-install task

    For 11 g : Wizard

    5. Deploy the dashboard images Post-install task

    6. Update the BI Physical Layer Connection to ODI Work Repository Post-install task

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    11/23

    11

    Installing LineageRequirements

    Java Runtime Environment 1.6 (JRE) Work Repository on Oracle database Stop BI Server and BI Presentation services component Backup the OBIEE RPD and Webcat

    RPD file used by the server is NOT open in BI Admin tool Install and execute OBIEE Lineage Wizard or Command

    Line tools on the machine where the BI Admin tool isinstalled

    The database user used to connect to the WorkRepository must have privileges to create views in theschema hosting the Work Repository

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    12/23

    12

    Installing LineageInstalling and Starting the OBIEE Lineage Wizard

    ODI Companion CD: /misc/biee-lineage/odiobilineage.zip

    1. Extract the contents of the zip file to a directory.

    2.Start the wizard from the /bin sub-folder: On UNIX operating systems:

    ./refreshlineage.sh On Windows operating systems:

    refreshlineage.bat

    Tip: You can also use theinstalllineage.bat

    script to start the wizard. Use no parameterswhen starting the script.

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    13/23

    13

    Installing Lineage and Deploying theLineage ArtifactsUsing the OBIEE Lineage Wizard

    Oracle Homedirectory for theOBIEE installation

    BIEE Repository(RPD) file

    OBIEE repositoryadministrator user

    name and password

    Screen depends onOBIEE version. Theversion is detected

    from the RPD selectedin the previous screen.

    Location of the OBIEEWeb Catalog

    Home Directory of your OBIEE InstanceFor example:C:\OBIEE\Middleware\instances\instance1 Name of the web catalog folder into

    which the Lineage Artifacts will bedeployed.

    For example: /shared

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    14/23

    14

    Post-Installation Tasks (OBIEE 10 g only)Deploy the Web Catalog Requests in the OBIEE 10 g Web Catalog

    The OBIEE/ODI Lineage comes with a Web Catalog for building your

    reports on top of the Lineage and ODI Repository tables.To import the Web Catalog requests:

    1. Connect to your Web Catalog.1. Connect to your Web Catalog.2. Expand the catalog and select the shared folder into which the

    ODI catalog items will be imported.3. Select File > Unarchive .4. In the Unarchive catalog window, enter in the Archive File Path

    field the location of the ODI catalog archive file. Note that this fileis located in the /artifacts/10g sub-folder of the Lineageinstallation folder:

    For OBIEE 10.1.3.3, enterartifacts/10godi_catalog_archive_10g.cat

    For OBIEE 10.1.3.4, enterartifacts/10g/odi_catalog_archive_10_1_3_4.cat

    5. Click OK . A new folder called ODI appears in the catalog folder.

    1. Connect to your Web Catalog.2. Expand the catalog and select the shared folder into which the ODI

    catalog items will be imported.

    1. Connect to your Web Catalog.2. Expand the catalog and select the shared folder into which the

    ODI catalog items will be imported.3. Select File > Unarchive .

    1. Connect to your Web Catalog.2. Expand the catalog and select the shared folder into which the

    ODI catalog items will be imported.3. Select File > Unarchive .4. In the Unarchive catalog window, enter in the Archive File Path

    field the location of the ODI catalog archive file. Note that this fileis located in the /artifacts/10g sub-folder of the Lineageinstallation folder:

    For OBIEE 10.1.3.3, enterartifacts/10godi_catalog_archive_10g.cat

    For OBIEE 10.1.3.4, enterartifacts/10g/odi_catalog_archive_10_1_3_4.cat

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    15/23

    15

    Post-Installation Tasks (OBIEE 10 g + 11 g )Deploy the Dashboard Images

    Prepackaged requests use images that must be deployed into the

    application server that hosts the analytic application Dashboard images ( hie.gif and lin.gif ) are located in the

    /artifacts/images sub-folder of the Lineage installation folder Copy these dashboard images to the res folder under the deployment

    directory of the BI analytics application.For example: For OBIEE 10g:

    \j2ee\home\applications\analytics\analytics\res

    For OBIEE 11g: \servers\\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    16/23

    16

    3. Expand the ORACLE_ODI_REPOSITORY database in the OBIEEPhysical Layer.

    Post-Installation Tasks (OBIEE 10 g + 11 g )Update the BI Physical Layer Connection to the ODI Work Repo

    1. Start the Oracle BI Administration tool.

    6. Expand the renamed schema and test this updated connection.

    2. Open the RPD file ( .rpd ) used by the BI Server.

    4. Edit the Connection Pool to match your ODI work repositoryconfiguration.

    5. Update the Physical schema to match the schema of the ODI WorkRepository

    Update the Datasource name field

    Update the Usernameand Password fields

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    17/23

    17

    Refreshing the LineageProcess Overview

    The lineage is refreshed when either ODI or OBIEE metadatahas changed

    To synchronize the lineage tables content with the activeOBIEE and ODI systems' metadata

    This refresh process:

    Extracts the OBIEE Metadata from a OBIEE Instance Consolidates the OBIEE and ODI Metadata in the Lineage

    Tables stored in the ODI Work Repository

    Requires a mapping :

    The ODI Data Model and the OBIEE Physical Database shouldcontain the same tables.

    ODI Data Model OBIEE Database

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    18/23

    18

    Refreshing the Lineage from Existing ExportsWith the OBIEE Lineage Wizard

    Refreshes the OBIEE Lineage from existing OBIEE Repository and Web

    Catalog exports created manually

    Tip: You can also use therefreshlineage.bat

    script instead of the wizard.

    1. Start the wizard from the /bin sub-folder: On UNIX operating systems:

    ./refreshlineage.sh On Windows operating systems:

    refreshlineage.bat2. Follow the instructions on the wizard screens

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    19/23

    19

    Refreshing the Lineage From Existing ExportsRefresh Lineage Wizard Flow

    The location of the repositoryexport file. This file isgenerated using the OBIEE

    Admin tool.

    The location of the web catalogexport file. This file isgenerated using the OBIEECatalog manager.

    ODI username and password.This user should haveSUPERVISOR privileges

    Database user name andpassword to connect to theschema (or database, library)that contains the ODI MasterRepository

    Driver name and URL toconnect to Master Repository

    Select a Work Rrepositoryattached to the MasterRepository

    Select the OBIEEphysical schema youwant to map

    Select the ODI Model you want tomap to this OBIEE schema

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    20/23

    20

    With OBIEE 10 g it is not possible to automaticallyexport the web catalog content

    perform a manual export

    1. Start the OBIEE Lineage wizard

    1. Follow the instructions on the wizard screens.

    Exporting Metadata from OBIEE andRefreshing the OBIEE Lineage

    Tip: You can also use the refresh lineage script instead

    of the OBIEE Lineage wizard.

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    21/23

    21

    Exporting Metadata from OBIEE andRefreshing the OBIEE LineageExport Wizard Flow

    Oracle Home directory forthe OBIEE installation

    BIEE Repository(RPD) file

    OBIEE repositoryadministrator username and password

    Screen depends on OBIEEversion. The version isdetected from the RPDpreviously selected.

    Location of the OBIEEWeb Catalog

    Home Directory of your OBIEEInstanceFor example:C:\OBIEE\Middleware\instances\instance1

    Name of the web catalog folder intowhich the Lineage Artifacts will bedeployed.

    For example: /shared

    ODI username and password.This user should haveSUPERVISOR privileges

    Database user name andpassword to connect to theschema (or database, library)that contains the ODI MasterRepository

    Driver name and URL toconnect to Master Repository

    Select a Work Rrepositoryattached to the MasterRepository

    Select the OBIEEphysical schema you

    want to map

    Select the ODI Model you want to

    map to this OBIEE schema

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    22/23

    Copyright 2010, Oracle. All rights reserved.

  • 8/10/2019 p.20 Pts Odi11g Lineage Obiee

    23/23

    Copyright 2010, Oracle. All rights reserved.