upgrade considerations and strategies for oracle business intelligence applications

<Insert Picture Here>

ORACLE PRODUCT

LOGO

Upgrade Considerations and Strategies for Oracle Business Intelligence Applications Hari Cherukupally Wasi Ahmed Vince Fonte

Principal Product Manager Sr. Director of Systems Development Solutions Architect Oracle Business Intelligence Ventura Foods The JM Smuckers Company

3

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.

Safe Harbor Statements

4


Agenda

•  OBIEE 11g •  Oracle BI Applications 7.9.6.3 •  OBIEE upgrade to 11g – A Case Study •  Oracle BI Applications upgrade to 7.9.6.3 – A Case Study

•  Q & A

5

OBIEE 11g

6

Integrated Suite of Tools Improves Decisions Oracle BI Foundation Suite

Office Integration

Ad-hoc Analysis

Scorecards

Secure Search

Strategy Maps

Geographic Visualization Embedded in Applications

Interactive Dashboards

Scenario Analysis

Production Reporting

Business Processes

Predictive Analysis

Mobile Tablet

7

Oracle BI Applications

An Overview

8

Oracle BI Applications Prebuilt Analytics for Oracle EBS, PeopleSoft, Siebel, JD Edwards, and SAP

•  Financials •  HR •  Procure & Spend •  Projects •  Supply Chain •  Order Management •  Logistics

•  Sales •  Marketing •  Service •  Contact Center •  Price •  Loyalty •  Strategic Planning

•  Planning & Forecasting •  Profitability Management

•  Financial Services •  Communications •  Healthcare •  Retail

9

Oracle BI Applications 7.9.6.3 New Release Concurrent with OBIEE11.1.1.5

•  Full suite of pre-built CRM and ERP Analytics offerings –  Siebel, PeopleSoft, JD Edwards, E-Business Suite

•  Built for and certified with OBIEE 11.1.1.5 –  Adopts 11g presentation features

•  Presentation hierarchies, master-detail linking, cascading prompts –  Adopts 11g security model

•  Role-based, not group-based –  Unlock new capabilities for BI Apps customers

•  Geospatial, scorecard, mobile support, systems management

•  Additional important certifications, including: –  Informatica 9.01 HF2 –  Teradata 13.10

•  Additional bug fixes and ETL optimizations

10

Uptake of 11g by BI Applications Customers

Two approaches: •  Upgrade to BI Applications 7.9.6.3

–  Certifies 11.1.1.5, out of the box support for 11g capabilities –  Recommended choice for net new implementations and existing

BI Apps customers needing 11.1.1.5 capabilities alike

•  Platform-only upgrade for existing BI Apps deployments –  Fully supported with OBIEE 11.1.1.5 but not without challenges –  Good option for heavily customized deployments with strong

need for 11.1.1.5 features

11


Upgrade

12

Why Upgrade? When to Upgrade ?

•  OLTP is Upgraded •  Latest OBIEE

–  has new features –  supports newer versions of databases –  has bug fixes

•  Latest BI Apps –  has desired content –  supports newer versions of Oracle

Applications sources –  Supports newer databases /appliances –  language support –  performance bug fixes

•  Potential cost savings on additional maintenance cost

–  OLTP Source is out of support –  Database is out of support –  BI component version is out of support

Best Window •  OLTP is upgraded •  Database is Migrated •  Reporting Solutions are consolidated

13

Upgrade Process

•  Upgrade process is just not the technical process - Requires a lot of planning and involvement from Database Administrators, Business Analysts, QA teams

•  Upgrade Team requires understanding of customization done in the implementation

•  Requires detailed documentation of any customizations and lots of testing

14

Upgrade to Oracle BI EE 11g

•  Platform only upgrades are most common •  Oracle BI EE Platform is typically backward compatible with older versions

Analytics Applications, so does not require upgrading the applications •  OBIEE 11.1.1.5 upgrades has significant changes in

–  Installation –  Metadata Model Consistency Checks –  Security –  Presentation Services

Oracle BI EE 11g

Oracle BI EE 10.1.3.x

15

Oracle BI Upgrade Assistant –  Orchestrates upgrade across Oracle BI EE (10.1.3.2+)

– Moves appropriate files to right places –  Initiates component upgrade routines – Migrates:

•  RPD including RPD Users and Groups to WLS LDAP •  Presentation Services Webcatalog •  Scheduler Schema (Delivers) •  BI Publisher Repository •  BI Publisher Schema

– Not migrated: Configuration files, Custom style sheets, JavaScript

16

Oracle BI Upgrade Assistant

17

BI Application Upgrade – Major Stages

Upgrade Data Warehouse schema

Upgrade the Application software OBIEE, Informatica, DAC

Upgrade DAC and Informatica repositories

Migrate Data

Upgrade BI repository Upgrade BI web catalog

Backup/Pre-requisites

Upgrade Transactional Database Schema

Perf

orm

seq

uent

ially

18

Web Catalog Upgrade §  NO UI based tool to analyze and merge reports/

dashboards §  Forward compatible with new BI Presentation

Services releases

Analytics Repository Upgrade §  Purposeful 3-way merge functionality §  Original OOTB, Customer Modified, Current OOTB §  Preserves customer changes and incorporates

Oracle enhancements

DAC metadata §  Diff tools to determine and reapply changes

ETL & Warehouse Upgrade §  Customization Methodology isolates customer changes §  Diff tools to determine and reapply changes §  DW model and data upgrade shipped with each release

Application Upgrade Methodology A

dmin

istr

atio

n

Met

adat

a

Oracle BI Presentation

Services

Dashboards by Role

Reports, Analysis / Analytic Workflows

Metrics / KPIs

Logical Model / Subject Areas

Physical Map

Oracle BI Server

Direct Access to

Source Data

Data Warehouse / Data Model

ETL

Load Process

Staging Area

Extraction Process D

AC

Federated Data Sources Siebel Oracle JDE PSFT EDW

Other

19

BI EE Metadata Merge Process Purposeful 3-Way Merge

1.  Perform Equalize process to identify renamed objects and to generate upgrade IDs for all objects

2.  Perform Equalize process to identify renamed objects and to generate upgrade IDs for all objects

3.  Decide how to resolve conflicts, and then merge

4.  Remove inconsistencies arising from the conflict resolution decisions

Original.rpd (from the prior release)

Equalized Customized.rpd (Current repository)

Equalized Latest Master.rpd

(latest release)

Merged.rpd Customized.rpd

+ Latest Master.rpd

Remove inconsistencies and test with latest data

Compare, Resolve conflicts Merge Changes

1 2

3

4

20

2 Approaches to Application Upgrade Merge vs Re-implement

Re-implement •  Reasonable Option when upgrading

from a release several generations ago

•  Little History – No SCDs, Snapshots or Balances

•  High Tolerance to Loss of History •  Customizations under control

–  Well Documented –  Knowledgeable staff

•  Data still intact in the source –  Not archived –  Not purged

Merge, Resolve, Upgrade •  Viable when Upgrading from recent

releases •  Retaining History is paramount •  Good option for heavily customized

deployments –  Customizations are complex and not easy to re-

apply –  Customizations followed best practices

•  Source Data is archived or purged

21


UPGRADING TO OBIEE11G Case Study – Ventura Foods

Informa(on Technology Services

Upgrade to 11g Upgrade Considera(on

E R I

Informa(on Technology Services 23

•  Implement GUI to work with Legacy Data & JDE (post migra>on)

•  Dashboards help assess impact of FOCUS •  Opera>onal Repor>ng

•  Build on exis>ng metrics •  Incorporate current GUI technology •  Build capability for User Created Queries

Project Approach – Strategic View

JDE Rollout Centric Opera>ons Dashboards, Financial

Dashboards, Sales Dashboards, Pre-‐Defined Reports, Pre-‐Defined and Ad hoc Reports

BPM Execu>ve Dashboards, Other

Business Units

BI Data Mining, Analy>cs,

Scenario Planning

Planning Strategic Planning,

Marke>ng, Budge>ng/Planning

Evolu>onary Approach

Focus on Finance, Sales, Ops

•  Implement features for Business Performance Management & Evolve to Business Intelligence

•  Use itera>ve development to beTer meet user requirements including power users, brokers, suppliers, and customer

6 mon

ths

4 mon

ths 3 mon

ths

3 mon

ths

Support Base JDE Roll Out

Business V

alue & Com

plexity

Time PLC

3 mon

ths


Current Reporting Architecture and Environment

DataTracker

User Created Reports


E TL CSV

Files

SQL

JDE TMS (DB2) TPMS (FoxPro)


Legacy (DB2) Legacy (DB2)


Single Integrated Platform

Integrated Data Warehouse with user-‐centric divisional marts

JDE

Legacy

TMS, TPMS, HRIS, PLC, Others Other External

Sources such as product data, industry, CBOT,

etc.


Architectural Options

Hardware (CPU, RAM, Disks)

Opera>ng System

Database

ETL

Data Marts

GUI

IBM i5 Series

AIX

IBM DB2 Enterprise

Inform-‐a>ca

Build

OBIEE11g

ORACLE

BI Apps:


Upgrade Consideration – Why the Upgrade? •  The ra>onale behind for us to upgrade are as follows:

►  Most important-‐ beTer “UI” compare to 10g. ►  Mobile availability – iPad deployment. ►  BeTer integra>on wit BI Publisher – JDE reports dependency. ►  Upgrade BI Apps/Data Marts. ►  BeTer Skins & Styles in 11g. ►  Look and feel of Charts . ►  Users input. ( COGNOS and OBIEE 10g)


Upgrade Consideration - Customization •  What happens to any customiza>on done in 10g?

►  Metadata in the RPD is migrated to 11g as part of the RPD. ►  Metadata in the RPD will be migrated intact which would include all hierarchies ►  If the customiza>ons are at the file level like XML message files or Skins and Styles,

then you will need to make those changes within 11g manually. ►  How about the addi>onal skins & style customiza>ons for look & feel?

•  Skins & Styles will need to be re-‐applied manually in 11g. ►  Are the look and feel of Charts affected post upgrade?

•  Some aspects of char>ng will change because a new char>ng engine is being deployed under 11g.

►  Dashboard and reports editors will be changed -‐ you will need some re-‐training. ►  Customiza>on of branding need to be redone as well?

-‐  Take a inventory of all of your customiza>on.


Upgrade Consideration - Security •  How does the security model convert?

-‐  Users and Groups that you may have in your 10g RPD file will be migrated into the Fusion Middleware component which has its own LDAP.

-‐  All securi>es are now maintained and administered in FUSION Middleware -‐  Need to have a good understanding and working knowledge of Web Logic Web

Server


Upgrade Consideration - Performance •  How about the cache in the enterprise environment?

•  Need to reset and re-‐load all cache. •  The cache files do not get migrated. You will need to re-‐cache your reports and dashboards. •  Load up with memory – 12GB looks like what did the trick in our lab semng..

•  What happens to customiza>ons in ETL mappings? ETL is not affected. The ETL is external to the upgrade.


Upgrade Consideration – Common Issues •  The Administrator user that existed in 10g no longer exists in 11g.

►  Manual re-‐work in this area. We did not find any easy way for conver>ng. ►  This is handled through Fusion Middleware Enterprise Manager as well as passwords. ►  Should have a good working knowledge of Weblogic. ►  Performance is beTer if you have J-‐Rocket java VM.

•  Most issues that have had are around consistency checks failing in the RPD and report func>onality not working as before in the catalog. ►  Much more rigorous checking

•  Memory – Needed far more memory than specified in MTR ►  12 GB seems to do the trick.


Upgrade Consideration - Timeline •  The >me for us to upgrade took about 8 weeks.

►  About 2 weeks to migrate and validate all RPDs and Marts. ►  About 4 weeks to resolve some specific informa>ca/AIX issue ►  3 weeks of tes>ng. ►  1 Weeks of training and re-‐valida>on.

33


UPGRADING BI APPLICATIONS Case Study - The J.M. Smucker Company

The J.M. Smucker Company The J.M. Smucker Company

Upgrade Considerations and Strategies for Oracle Business Intelligence Applications

Vince Fonte – Solution Architect – The J.M. Smucker Company


1897 •  Founded in 1897 by Jerome M. Smucker"

•  Headquartered in Orrville, Ohio"•  Leading North American brands"•  Family run for five generations"•  Commitment to integrity, trust,

and quality"

Background


Transformational Growth

$0.0 $1.0 $2.0 $3.0 $4.0 $5.0

FY2001 FY2003 FY2005 FY2007 FY2009 FY2011

Net Sales ($ in Millions)

$615 $1,270 $2,044

$3,758 $4,826

$2,148


Agenda •  Rationale •  Planning •  Process •  Lessons Learned •  Adoption •  Summary


Rationale •  Substantial Business Case to implement Procurement

and Spend subject area. OBIA 7.9.6 was a prerequisite for the business case.

•  Procurement and spend subject area would enable development of strategies to leverage our corporate purchases and organizations across the Company

•  Update to current version to prepare for the future


Planning •  Estimation Considerations

–  Number of subject areas already implemented and how customized were they?

–  Source systems – were they customized, are they upgrading or changing?

–  Knowledgeable staff – Solution Architect, ETL, and RPD. Have they been through an upgrade before? Highly recommend adding a solution architect consultant to the project who has been thru an OBIA upgrade before.

•  Timeline –  3 months with the following resources

•  Resources –  1 Solution Architect –  2-3 ETL Resources –  2-3 RPD Resources


Upgrade Process •  Reviewed Upgrade Enhancements and changes.

•  Prepared database for upgrade and baseline for regression testing.

•  Installed Upgrade software.

•  Upgraded DAC and Informatica Respository.

•  Upgrade (Replace) OBIA RPD and then merge with the existing RPD.


Upgrade Process - Continued •  Upgrade (Merge) OBI Webcat

•  Detail review of data model –  Goal was to remove customization made in prior subject areas and use

the out of the box if possible. •  Regression Test

•  Deploy


Lessons Learned •  Leverage Experience OBIA Upgrade Resources

–  We used Oracle Professional Services consultant as Solution Architect.

•  Limit project to the OBIA upgrade only. –  We also rolled out Procurement and spend subject area concurrently.

•  Limit customization to OBIA subject areas as you roll them out especially the ETL, Data Model, and RPD.

–  You will have to re-do them with each upgrade. –  Conform to OBIA’s customization process.

•  Stay connected with Oracle for patches

•  Regression Test - Ensures quality deliverable


Adoption •  Procurement and Spend subject area has been

very well received and they want more.

•  Planning wider rollout of procurement and spend subject area.


Summary •  Tie upgrade to business need.

•  Leverage Experience OBIA Upgrade Resources.

•  Limit project to the OBIA upgrade only.

•  Stay connected with Oracle for patches

45

Q&A

46

Useful Links http://download.oracle.com/docs/cd/E21764_01/bi.1111/e16452/toc.htm http://download.oracle.com/docs/cd/E20490_01/bia.7963/e19040/toc.htm

http://download.oracle.com/docs/cd/E12513_01/doc/bic.101/e12652/dacupgrade.htm#CIACAIFJ

47

BI Applications Demo Pods

Demo Pod Exhibit Hall (Pod #) Human Resources Analytics Moscone South (S278)

Supply Chain and Order Management Analytics Moscone South (S276)

CRM Analytics Moscone South (S281)

Financial Analytics Moscone South (S279)

Procurement and Spend Analytics Moscone South (S280)

Project Analytics Moscone South (S277)

Oracle EPM and BI Applications Dynamic Duo Moscone West (W134)

BI Applications Hands On Lab (HOL) Transform Oracle Applications Data into Insights with Oracle Business Intelligence Applications

Marriott Marquis - Salon 5/6

48

BI Applications Demo Pods – Moscone South

Moscone South Pods:

§  Human Resources Analytics (S278)

§  Supply Chain and Order Management Analytics (S276)

§  CRM Analytics (S281)

§  Financial Analytics (S279)

§  Procurement and Spend Analytics (S280)

§  Project Analytics (S277)

49

BI Applications Demo Pods – Moscone West Oracle EPM and BI Applications Dynamic Duo (W134)

50

The preceding 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.

Safe Harbor Statements