• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition
 

Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition

on

  • 3,729 views

Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition

Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition
Boris Dahav
Oracle Israel

Statistics

Views

Total Views
3,729
Views on SlideShare
3,728
Embed Views
1

Actions

Likes
0
Downloads
196
Comments
0

1 Embed 1

http://www.docshut.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • One of the key differentiators of Oracle BI EE is this notion of a common enterprise information model. Oracle BI EE leverages a unified metadata model, which is accessed by all of the end user tools, so every end user and every department has the same consistent view of information, tailored to their role. As a result, organizations no longer need to maintain multiple metadata environments for different types of users. Some leading BI tools still have different metadata for their ad hoc tools than they do for their reporting tools, or dashboarding tools. With Oracle BI EE, you “model once, deploy everywhere.” The metadata model consists of three tiers: The physical layer allows you to import the table structures of your existing data sources, so it’s simply a representation of your actual physical data structure The semantic object layer allows you to create a simplified semantic representation of multiple data sources, creating a greatly simplified model of your business defined in a way that aligns with how business people think of it. This is where you define your data hiearchy (e.g. Quarter rolls up to Year), define dimensions and measures for multi-dimensional analysis, and create pre-defined calculations (e.g. product profitability) that will be available to all users. Then, that business model can be further simplified and exposed to end users through a range of tools through the presentation layer, which appears to end users as a single data source with a single table structure of dimensions, measures, and derived measures. This common enterprise information model enables the business to define key metrics and calculations in once place, assuring that everyone has a consistent view of information (tailored to their role) and assuring alignment across departments. Achieving this type of enterprise alignment is a problem for many organizations today. For example, let’s take something like “product profitability.” In a typical organization, you may have a sales organization that keeps their information in a CRM or SFA solution, a service group that has their own knowledge base and service call data, and a manufacturing organization that has an ERP system. The sales organization look at a particular product that is selling well and based on their limited view assume that product is really profitable. The service organization may look at the same product based on a higher than average number of calls determines that it’s a product that is hurting service margins. The manufacturing organization may look at the same product and think that due to a spike in the cost of goods required to manufacture that product, the product has a low margin relative to other products and should be de-emphasized. Without a complete and consistent view of how the company defines “product profitability”, how will the organization achieve alignment between the 3 departments? Oracle BI EE solves this problem, providing one consistent view of information and one “version of the truth.”
  • Describe the properties that are shown. Next we will see how this maps to BI EE metadata concepts.
  • Here we have the equivalent metadata in BI EE – adding the Discoverer properties dialog from the previous screen for illustration..
  • Describe how the Discoverer properties map to the BI EE metadata properties.
  • Describe how the Discoverer properties map to the BI EE metadata properties.
  • Describe how the Discoverer properties map to the BI EE metadata properties.
  • Describe how the Discoverer properties map to the BI EE metadata properties.
  • Here is the join property dialog in Discoverer – a join defined between Products.Product Key and Sales Facts.Product key
  • Discoverer hierarchies map to drill paths in BI EE

Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition Presentation Transcript

  • Migrating a Discoverer System to Oracle Business Intelligence Enterprise Edition Boris Dahav Oracle
  • 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 Oracle BI Server OLTP & ODS Systems Data Warehouse Data Mart SAP, Oracle PeopleSoft, Siebel, Custom Apps Files Excel XML Business Process Optimized Data Access Services Intelligent Caching Services Financial Performance Management Applications Intelligent Request Generation Common Enterprise Information Model Reporting & Publishing Financial Reporting BI Publisher Interactive Reporting SQR Production Reporting Web Analysis Ad-hoc Analysis Proactive Detection and Alerts Microsoft Office Interactive Dashboards Insight Performance Action Set Goals Plan Monitor Analyze Report Align Hyperion Essbase
  • 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 Model Enables 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
  • 1 into 3 ?
  • 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
      • OracleBIserverin 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,'&quot;Q&quot;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 Applications Single or Multi-source Analytic Apps Built on OBIEE Sales Service & Contact Center Marketing Order Management & Fulfillment Supply Chain Financials Human Resources Packaged ETL Maps Universal Adapters IVR, ACD, CTI Hyperion MS Excel Other Data Sources DW Schema Oracle BI Applications Oracle BI Suite EE Ad-hoc Analysis Proactive Detection and Alerts MS Office Plug-in Reporting & Publishing Interactive Dashboards Disconnected Analytics Web Services
  •