Effectively Deploying and Managing Business Intelligence Implementations

2. Effectively Deploying and Managing Business Intelligence Implementations Nick Tuson Senior Director, BI Product Management - Oracle Session: CON9417

3. The following is intended to outline our general product direction. It is intendedfor 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 Corporation.

4. Program Agenda • Product Architecture • Commissioning BI • Maintaining BI Service Levels • Maintaining BI Security Policy • Commissioning Applications

5. Oracle Business Intelligence 11g Architecture Commission Maintain Service Levels Commission Applications BI Platform Maintain Security Policy

6. BI 11g Product Architecture Significant TCO Improvements • Extensive use of Oracle technology stack • WebLogic used as application server • Enterprise Manager used for systems management • Introduction of OPMN for BI System components • Centralized configuration management • Modify on central server, propagate to other servers • Horizontal and vertical scale out procedures • Security – Oracle Platform Security Services (OPSS) • Scriptable systems management and control

7. Leverage FMW Technologies • WLS (Web Logic Server) • Application server • Required on every OBIEE machine • OPMN (Oracle Process Management Network) • Used for distributed process start / stop / restart • Process recovery (optional), Process ‘Ping’ • Managed via EM • Can also be used for performance collection (DMS) • Required on every OBIEE machine

8. Leverage FMW Technologies • DMS (Dynamic Monitoring System) • Standard FMW performance data collection format • Allows collection of current / historic data • Can be persisted to database • ODL (Oracle Diagnostic Logging) • Defines standard FMW Logging content and format • Defines mechanisms for analysing diagnostics across s/w components and systems / Support for ECID (transaction ID)

9. Leverage FMW Technologies • OPSS (Oracle Platform Security Services) • Authentication Service / Authorization Service • Policy Management Service (Policy Store) • User and Role Management Service (Identity Store) • Credential Storage Service (CSF)* • CSF (Credential Store Framework) • CSF provides secure handling of credentials used in BI system – looking at SSL certificates

10. Leverage FMW Technologies • OPATCH / OPACK • Standard Oracle patching mechanism • Silent or attended – integrated with EM • Support for BI Apps • UA (Upgrade Assistant) • Standard oracle approach to simplify upgrade / rollback of patches

11. Architecture - Terminology • Oracle BI Domain – The overall Oracle BI EE system • WebLogic Domain - A set of WebLogic instances servicing one or more J2EE applications • Admin Server (WebLogic) – Provides management of both the WebLogic and BI Domain. A WebLogic Domain contains one Admin Server • Managed Server (WebLogic)– Contains deployed J2EE BI application components

12. Architecture - Terminology • Node Manager (WebLogic) – A daemon process that provides remote server start, stop and restart capabilities in addition to monitoring • Oracle BI System Components – BI Server, Presentation Server, Scheduler, Cluster Controller and Java host • Oracle BI J2EE Components – BI Publisher, BI Office, Action Framework Service, BI SAW Bridge Plugin, Security, Web Services for SOA

13. Oracle BI Architecture – Simple Install

14. Oracle BI Architecture – Enterprise Install

15. Oracle BI Clustering Architecture Oracle BI Domain Server 1 Server 2 WebLogic Domain Managed Server | Cluster Node 1 Node Manager Managed Server | Cluster Node 2 Node Manager Action Service BI Office BI Publisher Action Service BI Office BI Publisher Web Service SOA BI Plugin Security BI Plugin Security Web Service SOA Admin Server Admin Server Admin Console Enterprise Mgr Admin Console Enterprise Mgr BI System Component Cluster Oracle BI System Components Oracle BI System Components BI Server BI Scheduler Presentation Server Java Host BI Server BI Scheduler Presentation Server Java Host OPMN Cluster Controller OPMN Cluster Controller

16. Oracle Business Intelligence 11g Lifecycle Commission BI Maintain Service Levels Commission Applications BI Platform Maintain Security Policy

17. Installation Process And Options • Roadmap to installation • Read the release notes and doc (twice) • Is machine DHCP? • If YES, then install loopback adapter • Download files (‘shiphome’) • Unpack to required location • Run RCU to create schemas • Run installer • Install required files • Configure

18. Installation Process And Options • Repository Creation Utility (RCU) • This is used to create the supporting database schemas required by Oracle Fusion Middlware • Oracle BI EE has a single schema that is prompted for during install. This includes the scheduler and BI scorecard schemas and others. RCU also selects an MDS schema to be created. • Independent of the main Oracle BIEE install process • Unzip distribution file and run : \bin\rcu.bat (Win) or \bin\rcu script (Linux)

19. Repository Creation Utility

20. Installation Procedure and Options • Install Options • Simple • Easiest way to install Oracle BIEE – WLS Admin Server Only • Enterprise • Adds more options, e.g. Ports and Oracle Home names • Used for creating a new install • Performing a horizontal scale out to another machine • Software Only • Used for advanced configuration, only ‘file copy’ of install • Separate configuration phas • Used with Exalytics and BI Apps Installations

21. Install Technology • Oracle Inventory • Oracle Universal Installer (OUI) • Unified installer across Oracle products. • Sophisticated framework • Pre-req checks • Supports Inventory • Supports silent install • Supports ‘standalone’ and ‘advanced’ install • Operates in an ‘Interview’ style

22. Oracle Universal Installer

23. Oracle Universal Installer

24. Configuration Utility – Scale Out

25. Configuration Utility – Scale Out

26. Configuration Phase

27. Oracle Business Intelligence 11g Lifecycle Commission BI Maintain Service Levels Commission Applications BI Platform Maintain Security Policy

28. Virtualization

29. Deployment Options

30. Deployment Options For BI Availability • Active / Active • Admin Server Failover Option • Active / Passive (CFC) • Enterprise Deployment Guide • Disaster Recovery

31. High Availability for Oracle BI • Oracle BI EE achieves high availability through • Process replication • Highly available storage (database and shared file system) • To provide a highly available system, BI EE requires the following external services: • A fault tolerant HTTP load balancer • A highly available shared file system • A highly available database for Oracle BI Scheduler and fact tables • The following system components must be replicated (have at least two instances): • Presentation Services • Cluster Controller • Oracle BI Scheduler • BI Server • JavaHost

32. High Availability for Oracle BI • The following persistent data sources must be placed on the highly available shared file system: • RPD publishing directory: The server metadata is contained in the repository file (.rpd file) that is local to each BI Server. One BI Server is designated as a Master. Online changes to the rpd file are made on the Master BI Server, and these changes are replicated to other members of the cluster. • Oracle BI Presentation Catalog • Global cache (optional, but advisable for higher performance). The global cache capability offers support for a common query cache that stores cache seeding and purging events. The global cache is visible to all BI Servers in the cluster. • Scheduler scripts

33. High Availability for Oracle BI • A WebLogic cluster with at least two members is required to host the Oracle BI EE Java components such as the Oracle BI Presentation Services Plug-in and the authentication service.

34. WebTier WLS JavaComponents OBIEE SystemComponents

35. Active - Active • An Active-Active system deploys two or more active system instances • All instances handle requests concurrently • Advantages: • Provides High Availability • Minimal System Downtime • Highly Scalable Architecture • Disadvantages: • Requires a Load Balancer • Requires Shared Storage

36. Active – Active • WLS Admin Server Failover • Default deployment as a singleton • Not essential for WLS managed server availability • Can be deployed on shared storage to enable failover • Procedure documented in Enterprise Deployment Guide

37. Active - Passive (Cold Failover Cluster) • An Active-Passive system deploys an active instance that handles requests and a passive instance that is on standby. Also known as a Cold Failover Cluster • Advantages: • Increased Availability over Single Instance • Less Costly than Active-Active • Load Balancer not required • Disadvantages: • Not as scalable as Active-Active • Longer Downtime than Active-Active

38. Active / Passive (Cold Failover Cluster)

39. Enterprise Deployment Guide The Enterprise Deployment Guide (EDG) defines an architectural blueprint that captures Oracle's recommended best practices for a highly available and secure Oracle Business Intelligence deployment The best practices described in this blueprint use Oracle products from across the technology stack, including Oracle Database, Oracle Fusion Middleware, and Oracle Enterprise Manager Fusion Middleware Control

40. Enterprise Deployment Diagram (EDG) • Documented Best Practice • Database • Security • Middle tier Cluster • Firewall Configuration • Tested by Oracle

41. Disaster Recovery • It is different to High Availability • Protection of services in cases of natural disaster • Typically at an alternative geographic location • May be fewer services or resources at standby site • Relies on shared storage and replication • Synchronize the Application Tier after changes and patching • Synchronize the DB Tier (RCU schemas)

42. Disaster Recovery

43. Enterprise Management and LifecycleComprehensive Support in Enterprise Manager • Unified systems management • Across all components / entire lifecycle • Performance monitoring & tuning • Diagnostics & troubleshooting • Across single instance & clusters • 1-click scale-out & online clustering • Dynamic capacity management • Lifecycle and Management • Develop, test, deploy • Scale-out & tune • Patch & upgrade cycles

45. Oracle BI EE Management Pack Key benefits

46. Oracle BI EE Management Pack Manage your OBIEE11g/Exalytics environment • New OBIEE11g target types with home pages • BI Instance, BI Presentation Server, BI Cluster Controller, BI Java Host, BI Scheduler, BI Server • Essbase Server, Essbase Application • Guided discovery for Stand-alone or Exalytics deployments • Process Control for Instances & Components • HA recommendations based on current setup

47. Oracle BI EE Management Pack Track and Diagnose • Log viewer integration • Search and diagnose across your BI or Exalytics instance • Log file monitoring • Set thresholds on custom patterns in BI log files • Configuration Management • View, Search and compare configurations between components and across instances • Dashboards reports for usage and failures • Scheduler reports for failed and scheduled jobs

48. Fusion Middleware Control Demonstration

49. Oracle Business Intelligence 11g Lifecycle Commission BI Maintain Service Levels Commission Applications BI Platform Maintain Security Policy

50. Oracle BI SecurityIntegration with Identity Management • Strong security • Comprehensive SSL • Encrypted metadata catalog • Report encryption, watermarking & signing • Authentication & Single Sign-On • Integrates with corporate directories / SSO • Externalizes authentication • Easy to configure & setup • Application roles & authorization • Comprehensive set of application roles • Externalized for all metadata & data • Flexible authorization model