91314778 Upgrading From OBIEE 10g to OBIEE 11g Rittman Mead

T : +44 (0) 8446 697 995 or (888) 631 1410 (USA) E : [email protected] W: www.rittmanmead.com

Mark Rittman, Technical Director, Rittman MeadODTUG BI/EPM Seriously Practical Conference, Sydney 2011

Upgrading from OBIEE 10g to OBIEE 11g

mailto:[email protected]



• OBIEE 11g is a complete overhaul of OBIEE 10g and provides many new and enhanced features‣ Redesigned, task-based UI with single interface for all products‣ Enhanced OLAP analysis and support for Essbase as a data source‣ Action Framework for actionable intelligence‣ Enhancements to the RPD including

better support for complex hierarchies‣ Enterprise Manager for web-based

management of the BI cluster‣ Use of WebLogic as a JEE platform‣ Integration with Oracle Mapviewer

for location-based analysis



License Considerations

• There is no additional charge for upgrading from OBIEE 10g to OBIEE 11g‣ assuming you have paid for support (upgrade element)

• However the Scorecard & Strategy Management is $995/named user extra• WebLogic Server EE will need to be licensed for scale-out (horizontal clustering)‣ OBIEE 11g only ships with a limited use, WLS SE license

• Use of Essbase is also pay-extra• All three products now bundled up as

optional “Oracle BI Foundation Suite”



Security Upgrade

• Existing users and groups in the RPD will be moved to WebLogic‣ You will no longer create users and groups in the RPD‣ Users, groups and application roles are now created in WebLogic

• OBIEE 11g takes advantage of WebLogic and Oracle Platform Security Service‣ Flexible authorization model‣ Comprehensive set of application roles‣ Externalized for all metadata and data

• Existing Init Blocks and LDAP mappings from the RPD will be preserved‣ Best practice is to eventually move

these to WLS and OPSS• No “Administrator” user; default admin

user is now WLS admin user (“weblogic”)



Upgrade Process Overview

1. Read the manuals ;-) Especially platform support, new WLS architecture etc2. Use RCU to create BI Platform database schemas3. Install Oracle BI 11g using Universal Installer4. Use the Upgrade Assistant to upgrade metadata and schemas from 10g5. Configure Oracle BI and perform scale-up and scale-out as required6. Regression test dashboards, reports, actions etc



Pre-Upgrade Steps

• Collect the artifacts and connection details for the objects to be upgraded‣ The RPD file, together with an Administrator password‣ The Web Catalog, as a directory ‣ The Deliveries directory‣ The BI Publisher repository directory‣ Connection details for the following schemas

- The BI Scheduler (Delivers) schema (S_NQ_SCHED)- The BIP Scheduler schema

‣ Any customizations, CSS files, Javascript files etc• Transfer to a temporary directory on the BI 11g server



Repository Creation Utility (RCU)

• Used to create the BIPLATFORM schema• Contains tables previously held in separate schemas in OBIEE 10g‣ Scheduler‣ Usage Tracking‣ SA_SYSTEM

• Creates other supporting schemas required by FMW11g

• Can deploy to Oracle, SQL Server, DB/2• See Installation lesson and slides

for full details of usage



Installation of OBIEE 11g Software

• After the RCU is run, you can then run the main Universal Installer• Provides three options for install:

1. Simple - few options, basic install for development etc2. Enterprise - full options, including scale-out3. Software Only - for deploying to

existing FMW installation• Install followed by creation of BI Domain• Should take around 1 hr to run



The Upgrade Assistant

• Standard Oracle Fusion Middleware lifecycle application• Orchestrates upgrade from Oracle BI EE (10.1.3.2+)• Migrates:‣ RPD including RPD Users and Groups to WLS LDAP‣ Presentation Services Webcatalog‣ Scheduler Schema (Delivers)‣ BI Publisher Repository‣ BI Publisher Schema‣ 10g Security model to 11g

• Generates log files• Not migrated: Configuration files,

Custom style sheets, JavaScript



Upgrading the RPD and Catalog Step 1 : Select Objects

• Select the RPD to upgrade, enter Administrator username and password• Enter new password for 11g RPD

(used for encryption)‣ password must be >8 chars,

and contain at least 1 number• Select web catalog

and deliveries directory



Upgrading the RPD and Catalog Step 2 : Connect to WLS

• Enter connection details for WLS Admin Server• Warning - upgrade is taken “live” on this server, existing RPD and webcat

will be taken offline (but preserved)



Upgrading the RPD and Catalog Step 3 : Validate Connection

• If connection unsuccessful‣ Check that WLS is up‣ Check WLS username

and password



Upgrading the RPD and Catalog Step 4 : Start Upgrade

• Press Upgrade button to start process• Monitor progress and review final results• Upgrade should proceed and finish successfully, with results written to logs



Upgrading BI Publisher and Scheduler Components

• Re-run Upgrade Assistant to upgrade BI Publisher repository and scheduler schema, and BI Scheduler schema

• Requires database connection to old schemas, as BIPLATFORM 11g schema• Use Verify Instance option at the end

to check all aspect of upgrade



Items That Require Manual Migration

• OBIEE‣ 10g cluster not automatically upgraded - only sets up initial single node‣ Any Custom Style/Skin‣ Any custom XML Messages ‣ Any custom images/files uploaded to OC4J‣ Any changes to instanceconfig.xml, config.xml, NQSConfig.INI‣ Any custom jar files uploaded to Javahost‣ Scheduler Script Path‣ OBIPS User Pref Currencies Config file‣ OBIPS PDF Font map file

• BI Publisher‣ If BI Server Security is used, update to Admin page for Web Catalog source



Viewing the Upgraded RPD and Web Catalog

• Once migrated, you can view the upgraded RPD and webcat using EM



Re-Apply Configuration Changes using EM

• Changes and customizations made to NQSConfig.INI and InstanceConfig.XML will need to be re-applied‣ Most will now be performed using EM, Some will need to be manually added‣ See System Administrator's Guide for details of managed and manual settings



Re-apply Clustering

• The migrated BI Domain will only have a single node• Use scale-up and scale-out options to add extra system components, or hosts,

to the BI cluster (clustering is enabled automatically with OBIEE 11g)



So How Do I Run an Upgrade Project

• Technically, the process is simple - use the Upgrade Assistant• But in reality, there is more to the process‣ You need to understand the existing OBIEE 10g architecture‣ Assess key features of OBIEE 11g and build a business case‣ Define which systems are in-scope for the upgrade‣ Define acceptance criteria‣ Decide on upgrade approach‣ Define and agree testing strategy‣ Perform Proof of Capability (POC)‣ Create upgrade instance & Run Upgrade Assistant‣ Provide End-User Training‣ Testing‣ Release



OBIEE 11g upgrade process

ProvePlan

Release

Foundatio n

New Feature Integration

Adopt

Go/No Go Release

ReworkAcceptance Test

Initial Build

End User Training

Environment Build

• Overview of process



Other Upgrade Considerations

• Upgrading will give like-for-like functionality: you will need to then implement features such as hierarchical columns, maps, action framework etc

• Scale-out clustering requires WLS Enterprise Edition license• Regression test your reports. For example‣ Level-based measures work differently in 11g‣ SQL generated might be different‣ Row and subject-area security might need revisiting

• Typical Upgrade can take between a couple of days, and a few weeks‣ Depends on how many environments are being upgraded‣ Complexity of the RPD and web catalog (including custom XML)‣ Ability to automate regression testing‣ Degree to which customizations have to be re-implemented using 11g approach



Mark Rittman, Technical Director, Rittman MeadODTUG BI/EPM Seriously Practical Conference, Sydney 2011



Documents

91314778 Upgrading From OBIEE 10g to OBIEE 11g Rittman Mead