SURENDER SARA Email : SURENDER.SARA@ORABYTE.COM SURENDER.SARA@SERACONSULTING.US

1. 10GAS Building Corporate KPI’s - 101 SURENDER SARA Email : SURENDER.SARA@ORABYTE.COM SURENDER.SARA@SERACONSULTING.US

2. AGENDA – Show Me How! • Deployment Architecture • Create EULADMIN ( KPI Repository ) • Create BA ( Build Meaningful Data Relationships ) • Create Discoverer Plus Report ( Your KPI’S ) • Create Discoverer and 10gAS interface • Create Portal Page ( Your Dashboard ) • Add Discoverer report • Show a client Portal site

3. EUL The Discoverer End User Layer (EUL) is a server based, low maintenance, powerful metadata repository and query management engine for data warehouses and on-line transaction processing (OLTP) systems.  The EUL engine also automatically performs query redirection to summaries.  The EUL is centrally stored in the RDBMS for scalability and ease of maintenance. 

4. Business Areas • The most visible function of the End User Layer (EUL) is to manage information describing relational data in business terms, facilitating end user ad hoc query and reporting. • Discoverer provides this by storing multiple 'Business Areas' within each EUL.  Business areas can represent one or more subject areas, simplifying tables and columns into easy to understand folders and items of data. 

5. Decision Points For Architecture Choice • Are we 24*7 or 8*6 shop? • How many level of DMZ’s you need to secure your data? • How much Availability, Scalability, Response time are we looking at.

6. 8-6 Shops With Reasonable Load • Choose Two node Architecture • Scale your Middle tiers as user load increases for Middle Tier component usage • Scale your customer database using RAC • Always scale horizontally, add more as you grow.

7. 24 * 7 Shops • Use multiple load balanced Middle tiers that will take care of your server crashes • Cluster your instances ( processes spawned from same ORACLE_HOME software ) • To cluster all instances must be configured identically • Database can be protected using RAC or ACTIVE-PASSIVE failover database architecture

8. Typical Oracle Architecture

9. Architecture Details 10gAS

10. Client – Breakdown 1 • mod_oc4j sits within Oracle HTTP Server and (i) identifies the requests it needs to act on, (ii) determines which OC4J to route those requests to, and (iii) communicates with that process. • Mod_oc4j analyzes the response from OC4J and takes appropriate actions - ex. If a single sign on redirect is required. • Single Sign-On user accounts - A Single Sign-On user account accesses applications (including OracleAS Portal) with a single user name and password. • Once a user has entered his or her Single Sign-On user name and password for one application, he or she can access other applications without having to log in again.

11. Client – Breakdown 2 • You Login AS • http://portalprd4.imcglobal.com:7777/pls/portal ( middle tier ) • You Login request is passed to SSO delegated service AS to Infrastructure Server • http://hrsprd1.imcglobal.com:7778/sso/jsp/login.jsp?site2pst....

12. 10gAS Middle Tier – Breakdown 1 • Discoverer • Forms • home • HTTP_Server • OC4J_BI_Forms • OC4J_Portal • Reports Server • Web Cache • Management

13. 10gAS Database Tier – Breakdown 1 • HTTP_Server • OC4J_SECURITY • OID • Single Sign-On:orasso • Management

14. Breakdown OverView For KPI’s - 1

15. Deployment Architecture Overview

16. Identify Data Layer 1 • This is the custom database, one or more as shown in the diagrams above • Identify you dataset to be part of KPI’s, Existing data-marts is a great start. • The dataset can be centralized or decentralized. • In centralized model you have one EULADMIN which is public. • In decentralized you have multiple EUL’s with one public and all other private. • Once database and EUL’s where KPI’s are stored are identified you are ready to connect to your discoverer reports

17. Cogitate on Application Layer, 2

18. Web Enabled Discoverer • OracleAS Discoverer Plus - End users use this Java based component to create workbooks and store them in the Discoverer repository (EUL). • OracleAS Discoverer Viewer - End users use this HTML based component to execute your workbooks created using Discoverer Plus or Desktop. • OracleAS Discoverer Portlet Provider - The Discoverer Portlet Provider is the content delivery mechanism end users use to publish Discoverer workbooks to OracleAS Portal.

19. Client Server Discoverer • Oracle Discoverer Administrator - Business and information technology (IT) administrators use this component to create, maintain, and administer meta data and user access privileges. • Oracle Discoverer Desktop - End users use this client/server based component to create workbooks and store them in the Discoverer repository (EUL). • Integration - Key integration points with the Oracle Database, Oracle9i Application Server and Oracle E-Business Suite.

20. Role of Discover Application Layer in KPI’s • Decide if you want to graph your data. • If you do then you CANNOT use desktop edition tool to build your charts. Use PLUS • PLUS stores reports and graphs using Java Graphs. • Desktop used C++ based graphs which cannot be pulled from portal viewer.

21. Presentation Layer, 10g Portal Pages • 10gAS portal pages are build using portal page technology • We start plugging in Portlets on those pages • For Discoverer KPI’s oracle has discoverer Portlet interface • For each report and a graph you will have to add this portlet • Once you run the page oracle 10gAS will launch the Discover Viewer for drilldown and data display

22. Summary of KPI flow • Locate your source data. • Locate your KPI dataset, data-mart’s. • Build EULADMIN, BA, Plus reports. • From 10gAS middle tier make sure to set TNSNAMES.ora to all EULADMINS where Plus reports are stored. • Set general connection in EM console to these EULADMIN’s • Use these connections to interface Plus reports to Discoverer Portlet, various connection list will be shown at this point.