Hoosh Afsar Financial Engineer Fannie Mae Venkat Tummalapalli Senior Product Manager Oracle Corporation

2. Hoosh Afsar Financial Engineer Fannie Mae Venkat Tummalapalli Senior Product Manager Oracle Corporation

3. Extending the reach of Enterprise Manager 10g to monitor custom applications across the grid

4. Intrusion Detection Net*8 over ASO HTTP over SSL HTTP over SSL Net*8 over ASO Net*8 over ASO Legacy systems Stove-pipe architecture is rigid and does not scale well Corporate Network Public DMZ LDAP over SSL Internal LDAP Servers Internal Logging Server Intranet Firewall Extranet Firewall External Firewall Internet Secure Extranet Listeners Intranet Oracle9iAS Extranet Oracle9iAS Logging Server (centralized) Net*8 over ASO Others Interfaces 9iAS Intra 9iAS Extra Extranet Standby Database Intranet Clients Intranet Listeners Intranet Standby Database Tuxedo Server Authentication Server Internal Applications

5. Our Computing Grid is flexible Business Processes Trade Valuation Risk Management Financial Modeling Portfolio Management Adjust supply of, access to resources Analyzedemand for resources Simulation Engine Servers Farm of 100+ machines

6. Our Grid needs an extensibile system mgmt tool Real time alerting Root-cause Impact Analysis Provisioning Trending Oracle Eco-System

7. Fannie Mae’s use of EM: Assuring availability of a $1 billion/day trade valuation system SE Applications Reduce Automate Simplify Sun Fire 280R 8G RAM Scale Repository

8. 1 End Users Exhaustive individual component management: Admin Performance Software Deployment Oracle eBus Suite Oracle Collab Suite Oracle AS 10g Oracle9iAS OC4J J2EE Integration 2 Integrated Suite Management: Admin Performance Software Deployment Web Services Top Link Web Cache Wireless SSO Portal 3 Integrated Management of Oracle Products Oracle 10g Critical Management for Oracle Eco-System 4 Custom Applications Oracle Enterprise Manager 10g: Extensible solution for the Enterprise

9. Zero barrier to entry WebClient HTML Management Servlets JDBC Open Management Repository Managed Targets What Makes EM extensible ? Console API Repository API XML Standard API

10. Rapid Instrumentation What makes EM Extensible? - Declarative definition of new targets :XML You do not need to write oraTcl scripts or C data gatherer catridges. Coding time is reduced by orders of magnitude : from Months to Minutes - Public interface to management data: Well documented Repository schema You will be able to use your favorite tools to slice and dice the management data or to do ad-hoc reporting - Support for Open Management Standards WBEM, JMX

11. 3 3. Extend Console UI 2. Build custom UI’s and Report through Repository Access 2 • Define and instrument • target metrics 1 What are the integration Points ? EM Black Box Active Management Repository Agent Agent Agent

12. 3 3. UI Integration Higher cost – Most value 2 2. Repository Integration Medium cost – Greater Value 1 1. Metric Instrumentation Low cost -- Immediate Value Integration Investment Value Curve Management Value for Customer Integration Investment (Time and Resources)

13. Integration Points: Agent • Function • Monitor the functioning of hardware or software targets. • Public access via • XML • Declarative discovery of target (targets.xml) • Declarative definition of metrics (metadata for target) • Fetchlets • data access mechanism • SQL, Log file, OS, SNMP, URL Timing, … • Instant value to your integration: Automatically shows up in the EM UI without having to do any UI changes!

14. Config File Integration Points: Agent Collection Definitions Collector Task Executor Transfer Metric Engine Target Metadata Fetchlet 1 Fetchlet 2 Fetchlet 3 Java API XMI V 1.2

15. Collector Metric Engine Task Executor Etc... Managed Targets Preconfigured WBEM Enabled User Defined Managed Target EM Agent Presentation API V 1.1

16. DB 1 DB 2 LOGIN Server Managed Target : Examples .. Middle Tier Backend JS Apache 1 App 1 BIG IP JS JS Apache 2 Cisco Router JS Apache 3 JS JS V 1.1

17. Integration Points : Repository • Functions • Uploads data into the database from loader files • Rollups of raw data • Notifications for event occurrences • Global Inventory for tracking software patch levels • Public access via • Views (ad-hoc reporting) • pl/sql api (procedural access, example add an admin)

18. Central Policy Inventory Application Level DB Config Monitoring Public “MGMT_” Level ECM & APM Internal Table Level Management Repository V 1.1

19. Integration Points: User Interface • Create homepages for your custom targets • Plug in administration components that are based off data collected in the repository. • The administration components can directly connect to targets or go thru the Agent to make changes on managed node.

20. June 2000 Internet Management Repository Notifications HTTP(S) XML XML Firewall Putting it all together Managed Targets EM Daemon Real-time Monitoring Reporting Notification Target Definition Files Metric Definitions Metric Data Alerts Client Response Times Web Server Response Times Information Rollup V 1.3

21. Example: Simulation Engine Queues

22. How do I instrument my app ? Prerequisite • Separate the application into multiple targets, and define them separately • Determine what makes up the application: • Components • Availability • Performance

23. How do I instrument my app ? Workflow Define target type • Define targets • pick your metric • compute metric • Define collections • collection schedule • Instantiate your targets using the EM UI. Define collections Set thresholds Declare the targets

24. EM SDK Provides Predefined Collection Mechanisms: Fetchlets Example Fetchlets: SQL and PL/SQL, SNMP, HTTP, Text, WEBM… Targets.xml Collections.xml <targetname>.xml Define the targets you want to monitor and the metrics you want to collect using XML Monitoring data immediately available from EM Console How do I instrument my app ? Agent

25. Example : What makes up my app ?

26. Are my applications available?

27. Example: App specific metrics

28. Example: App specific metrics

29. - <TargetMetadata META_VER="1.0" TYPE="fanniemae_vn_queue"> - <Display> • <Label NLSID="fanniemae_vn_queue_name">FANNIEMAE VN Queue</Label> • </Display> - <Metric NAME="Response" TYPE="TABLE"> - <Display> • <Label NLSID="vn_qparse">Response</Label> • </Display> - <TableDescriptor> - <ColumnDescriptor NAME="response_time" TYPE="NUMBER" IS_KEY="FALSE" TRANSIENT="TRUE"> - <Display> • <Label NLSID="vn_qparse">VN Queue Response Time (ms)</Label> • </Display> • </ColumnDescriptor> - • </Display> • </ColumnDescriptor> - <ColumnDescriptor NAME="Status_Message" TYPE="STRING" IS_KEY="FALSE"> - <Display> • <Label NLSID="vn_qparse">UpDown Status Message</Label> Step 1: How do I define a target? • > - < - • >

30. Step 2: How do I define collections ?

31. Step 3: How do I set thresholds ?

32. Step4: Declaring target instances

33. Step 5: Quality Assurance • Test metrics using the EM Metrics Browser • Setup collections into the repository - Edit emd.properties and specify Repository upload URL, Upload Interval • The custom application is now ready to be monitored by EM !

34. What did it buy for us ? • The data that we collect will now be uploaded/ rolled up periodically - Raw data -> hourly -> daily -> .. • Time Series charts with various statistical data for trending- Average, High/Low Watermark, Std Dev. • Event detection and real time notifications • Correlation across various layers of the FM stack • Service level reporting

35. When will it be available ? • 1st planned release : End of CY 2003

36. Q & Q U E S T I O N S A N S W E R S A