Integrating Data in Oracle BI
19.1 Introduction
OBIEE users need to know the origin of the data displayed on their reports. When this data is loaded from source systems into the data warehouse using ODI, it is possible to use the Oracle Data Integrator Lineage for Oracle Business Intelligence feature to consolidate Oracle Data Integrator ODI metadata with Oracle Business Intelligence Enterprise Edition OBIEE and expose this metadata in a report-to-source data lineage dashboards in OBIEE.19.1.1 Components
The OBIEE Lineage is made up of the following components: ■ Lineage Tables : These tables consolidate both the OBIEE and ODI metadata. They are stored in the ODI Work Repository. ■ Lineage Artifacts for OBIEE : This pre-packaged OBIEE artifacts are deployed in OBIEE to access the lineage information. These include: – Lineage RPD containing the Physical, Logical and Presentation layers to access the Lineage Tables, – Lineage Web Catalog Requests to be used in existing dashboard to create report -to-source dashboards, – Images used in these dashboards. ■ Command Line Tools and a Wizard to automate the lineage tasks: 2 Product TitleBookTitle as a Variable – 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.19.1.2 Lineage Lifecycle
This section describes the different phases of using OBIEE Lineage and the persons involved in these phases.19.1.2.1 Setting up the Lineage
OBIEE or ODI administrators set up the lineage process. Setting up this process is required once and consists of the following tasks: 1. Deploying the Lineage Artifacts for OBIEE 2. Configuring and automating the ExtractionConsolidation Refresh Process19.1.2.2 Refreshing the Lineage
OBIEE or ODI project managers refresh the lineage when either ODI or OBIEE metadata has changed, to synchronize the lineage tables content with their active OBIEE and ODI systems’ metadata. This refresh process:1. Extracts the OBIEE Metadata from a OBIEE Instance
2. Consolidates the OBIEE and ODI Metadata in the Lineage Tables stored in the ODI
Work Repository. During this phase, a correspondence between the ODI Data Models and the OBIEE Physical Databases must be provided. By doing this mapping, you indicate that an existing model definition in Oracle Data Integrator corresponds to an existing database in OBIEE. These two should contain the same tables. By providing this mapping information, you enable the lineage to consolidate the OBIEE and ODI metadata and build an end-to-end lineage.19.1.2.3 Using the Lineage
The lineage is used to extend existing dashboards. You can create specific links in these dashboards to browse the data lineage and view the execution statistics of the ODI sessions. You can also customize your own dashboards using the pre-packaged Lineage Artifacts for OBIEE. Figure 19–1 describes the Lineage lifecycle after the initial setup. 3 Figure 19–1 Lineage Lifecycle This image describes the Lineage lifecycle after the initial setup. The BIEE metadata is extracted 1 and consolidated with the ODI Metadata in the lineage tables 2. The lineage tables are accessed from the end-user’s dashboard 3 through the Lineage Artifacts deployed in the BIEE Server.19.2 Installing the Lineage in an OBIEE Server
This section contains information and instructions for installing OBIEE Lineage: ■ Installation Overview ■ Requirements ■ Installation Instructions ■ Post-Installation Tasks19.2.1 Installation Overview
Installing Lineage in an OBIEE Server deploys the required OBIEE artifacts in the OBIEE Repository and Web Catalog. The OBIEE Lineage artifacts are the Lineage RPD, the Lineage Web Catalog Requests, and the dashboard images. These artifacts are used to access the lineage content from your reports and dashboards. The installation is performed using the OBIEE Lineage Wizard. This wizard guides you through the installation, and also through the configuration and refresh of the Oracle Data Integrator ODI Lineage for Oracle Business Intelligence Enterprise edition OBIEE. After installation and configuration are complete, there are some post-installation tasks you need to perform, depending on your OBIEE version. The complete installation flow is as follows:Parts
» Oracle Fusion Middleware Online Documentation Library
» Terminology Using This Guide
» Concepts Knowledge Modules Introduction
» System Requirements and Certifications
» Using External Tables Technology Specific Requirements
» Using Oracle Streams Technology Specific Requirements
» Connectivity Requirements Installation and Configuration
» Creating an Oracle Physical Schema
» Setting Up an Integration Project
» Reverse-engineer an Oracle Model
» Setting up Changed Data Capture
» Designing an ETL-Style Interface
» Troubleshooting Oracle Database Errors Common Problems and Solutions
» System Requirements and Certifications Technology Specific Requirements
» Creating a File Physical Schema
» In the Models accordion, right click your File Model and select New Datastore.
» In the editor toolbar, click Reverse-Engineer.The Columns Setup Wizard is
» Click OK when the columns definition is complete. From the File main menu, select Save.
» In the Definition Tab, enter the following fields:
» Go to the Files tab to describe the type of file. Set the fields as follows:
» In the toolbar menu, click Reverse Engineer COBOL CopyBook.
» Click OK. COBOL Copybook reverse-engineering
» Create an ODBC Datasource for the Excel Spreadsheet
» Define the Data Server, Physical and Logical Schema for the Microsoft Excel
» Run the customized reverse-engineering
» Select the Microsoft Excel Driver .xls driver.
» Name the data source: ODI_EXCEL_FILE_REPO and select the file
» In Topology Navigator, add a Microsoft Excel data server with the following
» From the File main menu, select Save.
» Add a physical schema to this data server. Leave the default values in the
» In the Context tab of the physical schema, click Add.
» In the new line, select the context that will be used for reverse engineering and
» In the Reverse-Engineer Tab, set the following parameters:
» In the toolbar menu, click Reverse-Engineer.
» Technology-Specific Requirements Installation and Configuration
» Reverse-engineer a Data Model
» Loading Data from an ANSI SQL-92 Compliant Technology
» Loading Data to an ANSI SQL-92 Compliant Technology
» Integrating Data in an ANSI SQL-92 Compliant Technology
» System Requirements Installation and Configuration
» Technologic Specific Requirements Installation and Configuration
» Creating a Physical Schema for XML
» Reverse-Engineering an XML Model
» Synchronizing XML File and Schema
» Loading Data from an XML Schema
» Loading Data to an XML Schema
» Detect the Errors Coming from XML Common Errors
» Creating a Complex File Physical Schema
» Designing an Interface Oracle Fusion Middleware Online Documentation Library
» Using the BULK INSERT Command
» Using Linked Servers Technology Specific Requirements
» Creating a Microsoft SQL Server Physical Schema
» Create a Microsoft SQL Server Model
» Reverse-engineer a Microsoft SQL Server Model
» Loading Data from Microsoft SQL Server
» Integrating Data in Microsoft SQL Server
» Creating a Microsoft Excel Data Server
» Creating a Microsoft Excel Physical Schema
» Setting up Data Quality Setting Up an Integration Project
» Create a Microsoft Excel Model
» Reverse-engineer a Microsoft Excel Model
» Loading Data from Microsoft Excel
» Loading Data to Microsoft Excel
» Decoding Error Messages Common Problems and Solutions
» Specific Requirements Oracle Fusion Middleware Online Documentation Library
» Creating a Netezza Physical Schema
» Reverse-engineer a Netezza Model
» Loading Data from Netezza Loading Data to Netezza
» Creating a Teradata Physical Schema
» Reverse-engineer a Teradata Model
» Loading Data from Teradata Loading Data to Teradata
» Integrating Data in Teradata
» Primary Indexes and Statistics
» Support for Teradata Utilities Support for Named Pipes Optimized Management of Temporary Tables
» Creating a Hypersonic SQL Data Server
» Creating a Hypersonic SQL Physical Schema
» Setting up Changed Data Capture Setting up Data Quality Designing an Interface
» Introduction Oracle Fusion Middleware Online Documentation Library
» Concepts Knowledge Modules Oracle Fusion Middleware Online Documentation Library
» Creating a DB2400 Physical Schema
» Reverse-engineer an IBM DB2400 Model
» Setting up Trigger-Based CDC
» CDCRTVJRN Program Details Setting up Log-Based CDC
» Using the CDC with the Native Journals
» Problems While Reading Journals
» Loading Data from IBM DB2 for iSeries
» Loading Data to IBM DB2 for iSeries
» Integrating Data in IBM DB2 for iSeries
» Installing the Run-Time Agent on iSeries
» Using Client Access Alternative Connectivity Methods for iSeries
» Change the driver and URL to your AS400 server with the following information:
» Set the following java properties for the java machine the run-time agent deployed
» Troubleshooting Error messages Troubleshooting
» Connection Errors Common Problems and Solutions
» Integrating Data in Oracle BI
» Extracts the OBIEE Metadata from a OBIEE Instance
» Using the Lineage Lineage Lifecycle
» Installation Overview Installing the Lineage in an OBIEE Server
» Requirements Installing the Lineage in an OBIEE Server
» Post-Installation Tasks Installing the Lineage in an OBIEE Server
» Exporting the OBIEE Repository Documentation to a Text File
» Exporting the OBIEE Web Catalog Report to a Text File
» Refreshing the OBIEE Lineage From Existing Exports
» Configuring the Scripts Automating the Lineage Tasks
» Automating Lineage Deployment Automating Lineage Refresh
» Viewing Execution Statistics Viewing and Filtering Lineage Data
» Using the Dashboard Using the Lineage in OBIEE Dashboards
» Using Lineage and Hierarchy Using Contextual Lineage
» Reverse-engineer an Essbase Model
» Loading Metadata Designing an Interface
» Loading Data Designing an Interface
» Data Extraction Methods for Essbase
» Extracting Essbase Data Extracting Data
» Extracting Members from Metadata
» Creating an Hyperion Financial Management Data Server
» Creating an Hyperion Financial Management Physical Schema
» Create an Financial Management Model
» Reverse-Engineer an Financial Management Model
» Extracting Financial Management Data
» Extracting Members from Member Lists
» Data Store Tables Oracle Fusion Middleware Online Documentation Library
» Creating an Hyperion Planning Data Server
» Creating an Hyperion Planning Physical Schema
» Reverse-engineer a Planning Model
» Log on to Planning Web. Select Administration Data Load Administration.
» Accounts Datastore Tables and Data Load Columns
» Employee Datastore Tables and Data Load Columns
» Entities Datastore Tables and Data Load Columns
» User-Defined Dimensions Datastore Tables and Data Load Columns
» Attribute Dimensions Datastore Tables and Data Load Columns
» JMS Message Structure Concepts
» Creating a JMS Physical Schema
» Create a JMS Model Defining the JMS Datastores
» Loading Data from a JMS Source Integrating Data in a JMS Target
» Declaring JMS Properties Using JMS Properties
» Using Property Values as Source Data
» Setting Properties when Sending a Message
» Creating a JMS XML Physical Schema
» Reverse-Engineering a JMS XML Model
» Loading Data from a JMS XML Source Integrating Data in a JMS XML Target
» Creating a Physical Schema for LDAP
» Reverse-Engineering an LDAP Model
» Loading Data from an LDAP Directory
» Loading Data to an LDAP Directory
» Integrating Data in an LDAP Directory
» Setting Up an Integration Project Troubleshooting
» Creating a TimesTen Physical Schema
» Reverse-engineer a TimesTen Model
» Setting Up an Integration Project Setting up Data Quality
» Integrating Data in TimesTen
» Create an Attunity Stream Model Reverse-engineer an Attunity Stream Model
» Setting Up an Integration Project Designing an Interface Using the LKM Attunity to SQL
» Overview of the GoldeGate CDC Process
» Create the Staging Physical Schema
» Define the Source Data Server
» Create the Source Physical Schema
» Create the Replicated Tables
» Set Up an Integration Project
» Configure CDC for the Replicated Tables
» Configure and Start Oracle GoldenGate Processes
» Design Interfaces Using Replicated Data
» Initial Load Method Advanced Configuration
» Tuning Replication Performances Advanced Configuration
» One Source Multiple Staging Configuration
» Cross Reference Table Structures
» Loading Phase LKM Overview of the SOA XREF KM Process
» Defining the Topology Working with XREF using the SOA Cross References KMs
Show more