<Insert Picture Here>

Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition Boris DahavOracle

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

• Stay on Discoverer• Continued new releases and functionality• Dedicated development team• Covered by Oracle’s Lifetime Support• No forced migration

• Use Discoverer with BI Enterprise Edition• Discoverer integration with BI Publisher• Discoverer analysis surfaced in BI EE Dashboards• Use BI EE Delivers for alerting & Distribution on Discoverer

Analysis

• Migrate Discoverer to BI Enterprise Edition

Oracle BI Discoverer – Options

"This information is not a commitment to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle"

Migrates only the metadata!

Reports are expected with rel. 11

Oracle BI Suite Enterprise Edition Plus

OracleBI Server

Ad-hoc Analysis

ProactiveDetectionand Alerts

Microsoft Office

Interactive Dashboards

OLTP & ODSSystems

DataWarehouseData Mart

SAP, OraclePeopleSoft, Siebel,

Custom Apps

FilesExcelXML

BusinessProcess

Optimized Data Access Services

Intelligent Caching Services

Financial Performance Management Applications

InsightPerformance

Action

SetGoals

Plan

Monitor

Analyze

Report

Align

HyperionEssbase

Intelligent Request Generation

Common Enterprise Information Model

Reporting & Publishing

Financial Reporting

BI Publisher

Interactive Reporting

SQR Production Reporting

Web Analysis

Benefits of Oracle BI EE

• Easier to access multiple different data sources simultaneously

• Hot Pluggable with existing investments• Dashboards offer interactivity and greater presentation

capability• Pure thin client interface throughout• Alerting, scheduling and distribution• Production reporting with BI Publisher

<Insert Picture Here>

Product Components

Product Components

• Discoverer Administrator <> BI EE Administration Tool

Product Components

• Discoverer Plus/Viewer <> BI EE Answers

Product Components

• Discoverer Portlet Provider <> BI EE Dashboards

<Insert Picture Here>

Metadata Migration

Common Enterprise Information ModelEnables Consistency, Security, Reuse, Flexibility

Role-based views of the information relevant to the user

Consistent definition of business measures, metrics, calculations

Model once, deploy everywhere

Across any data sources

• User roles, preferences• Simplified view• Logical SQL interface

• Dimensions• Hierarchies• Measures• Calculations• Aggregation Rules• Time Series

• Map Physical Data• Connections• Schema

Presentation Layer

Physical Layer

Semantic Object Layer

Physical Layer

Connection Pool

Object mappings

Primary / foreign keys

Business Model Layer

Dimensional Model

Dimensions

Facts

Hierarchies

Presentation Layer

End users view

Used to build requests in Answers

Migration Approach

• Map objects with similar metadata concepts…..

• End User Layer• Business Areas• Folders and Items• Joins• Hierarchies

Migration Approach

• End User Layer (EUL)• Discoverer metadata repository• Schema in a database

• BI Enterprise Edition RPD file• Metadata repository file

Migration Approach

• Map objects with similar metadata concepts…..

• End User Layer• Business Areas• Folders and Items• Joins• Hierarchies

Migration Approach

• Business Areas → Presentation Layer Catalog

• Business Areas → Answers Subject Area

Migration Approach

Migration Approach

• Map objects with similar metadata concepts…..

• End User Layer• Business Areas• Folders and Items• Joins• Hierarchies

Folders

From Discoverer

From Discoverer

From Discoverer

From Discoverer

Migration Approach

• Map objects with similar metadata concepts…..

• End User Layer• Business Areas • Folders and Items• Joins• Hierarchies

Joins

From Discoverer

Physical Layer Joins

From Discoverer

Physical Layer Joins

From Discoverer

Business Model Joins

From Discoverer

Business Model Joins

From Discoverer

Business Model Joins

Migration Approach

• Map objects with similar metadata concepts…..

• End User Layer• Business Areas • Folders and Items• Joins• Hierarchies

Hierarchies

DEMO

• Configuration Options• Simple Command Line Run

Migration Challenges And Handling

• Key Identification• Measure Identification

• Sum

• Count (Primary Key Columns)

• Count Distinct (Foreign Key)

• Multiple Joins • Multiple Join Paths

• Multiple Join Columns

• Circular Joins

• Chasm Traps / Fan Traps• Complex Folders• Custom PL*SQL Functions / Oracle Analytic Functions

Multiple-Joins

Star Schema

Migration Fidelity

• Anticipate some manual intervention• 80-20 rule! (Closer to 90-10?)

• Manual Intervention Scenarios• EUL_DATE_TRUNC Functions nesting!• Joins between different Datatypes• No Item Class equivalent in BI EE

• LOVs are generated at run time

• OTHERS…Documentation has summary

• Multi-Byte Supported• Error/Log Messages in English only

<Insert Picture Here>

Tachless

Tachless

• Prerequisite• The minimum version of Discoverer EUL that can be used with the Assistant

is 10.1.2.n

• Oracle BI EE that the Assistant is run against but must be a minimum of 10.1.3.4.

• Stages• Export the Discoverer metadata you wish to convert to an .eex file using the

Discoverer Administration tool

• OracleBI\server\bin \MigrateEUL.exe filename.eex

• filename.migration.log - captures the progress of migration at a high level

• filename.exception.log - captures the items that could not be migrated such as skipped joins and folders

What to expect 1

What to expect 2

What to expect 3

• Discoverer “knows” it’s working on Oracle DB • OBIEE Doesn’t (works with many data sources)• Result: Extensive usage of Evaluate function instead

of original DB function• “Discoverer calculated items based on Oracle PL/SQL functions or Oracle

analytic functions will be migrated to Oracle BI EE metadata that uses the EVALUATE and EVALUATE_AGGR functions. These calculations will be created as a logical column with its formula being set in the Physical Mapping

of the Logical Table Source. ”• EUL_DATE_TRUNC(Transaction Date,'"Q"Q')

Evaluate( DECODE( %1, NULL, TO_DATE('01011900','MMDDYYYY'), TRUNC( %1, 'Q')),TIMES.TRANSACTION_DATE)

<Insert Picture Here>

Migration Considerations

Migration Considerations

• What type of system do you wish to migrate?• Data warehouse

• Typical a reasonably shaped STAR Schema in the Physical

• Recommendation• Use ConsiderMultiplePaths = FALSE

• Review Result & Apply gaps manually or regenerate after careful review of Skipped joins

• 3NF/OLTP Schema

• Custom build Discoverer metadata/reports on a Transactional Schema

• More complexities when translating into OBIEE• May require multiple iterations, use of Configuration parameters and some

manual overrides

• Oracle Applications reporting (e.g. BIS)• Pre-delivered content from Oracle EBS Suite with some onsite customizations• Strong candidate for Oracle BI Applications

Oracle BI ApplicationsSingle or Multi-source Analytic Apps Built on OBIEE

Oracle BI Suite EE

Ad-hoc Analysis

ProactiveDetectionand Alerts

MS OfficePlug-in

Reporting & Publishing

Interactive Dashboards

DisconnectedAnalytics

WebServices

SalesService &Contact Center

Marketing

Order Management& Fulfillment

Supply Chain

FinancialsHuman

Resources

PackagedETL Maps

UniversalAdapters

IVR, ACD, CTIHyperionMS Excel

Other Data SourcesDW Schema

Oracle BI Applications