Hoosh AfsarFinancial EngineerFannie Mae

Venkat Tummalapalli Senior Product ManagerOracle Corporation

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

Stove-pipe architecture is rigid and does not scale well

IntranetListeners

HTTPover SSL

Net*8over ASO

LDAP over SSL

IntrusionDetection

SecureExtranetListeners

ExternalFirewall

ExtranetStandby

Database

AuthenticationServer

ExtranetFirewall

IntranetClients

InternalLDAP

Servers

Net*8over ASO

Net*8over ASO

HTTPover SSL

LoggingServer

(centralized)

IntranetFirewall

Corporate Network

Legacysystems

Net*8over ASO

Tuxedo Server

9iASIntra

IntranetOracle9iAS

IntranetStandby

Database

9iASExtra

ExtranetOracle9iAS

OthersInterfaces

InternalApplications

Public DMZ

Internet

Internal Logging Server

Our Computing Grid is flexible

Analyze demand

for resources

Adjust supply of, access to resources

Simulation Engine Servers

Business ProcessesTrade ValuationTrade Valuation

Financial ModelingFinancial Modeling

Portfolio ManagementPortfolio Management

Risk Risk ManagementManagement

Farm of 100+ machines

Oracle Eco-System

Our Grid needs an extensibile system mgmt tool

SEES

EnterpriseServer

SE-Agent

AgentServer

SE-Server

Computation Server

...

SE-Agent

AgentServer

SE-Server

Computation Server

...

SE Client

Client hostRoot-cause Impact Analysis

Trending Provisioning

Real time alerting

Fannie Mae’s use of EM: Assuring availability of a $1

billion/day trade valuation system

Repository

Automate

Simplify

Scale

Reduce SE Applications

Sun Fire 280R 8G RAM

Oracle Enterprise Manager 10g: Extensible solution for the Enterprise

End Users

Integrated Management of Oracle Products

Oracle Collab Suite

3

Oracle eBus Suite

Oracle 10g

Oracle9iASOC4J

Exhaustive individualcomponent

management:Admin

PerformanceSoftware Deployment

1

Integrated SuiteManagement:

AdminPerformance

Software Deployment

Web Services Top Link

Integration

Portal

Web Cache

SSOWireless

Oracle AS 10gJ2EE

2

CriticalManagement for

Oracle Eco-System

4 CustomApplications

What Makes EM extensible ?WebWeb ClientClient

Managed TargetsManaged Targets

Open Management RepositoryOpen Management Repository Repository API

XML

JDBC

Standard API

Management ServletsManagement Servlets

HTML

Console API

Zero barrier to entry

What makes EM Extensible?

- Declarative definition of new targets :XMLYou 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 schemaYou 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

Rapid Instrumentation

What are the integration Points ?

AgentAgent

1. Define and instrument target metrics 1

Agent

ActiveManagementRepository

2. Build custom UI’s and Report through Repository

Access2

3. Extend Console UI 3

EM Black Box

Integration Investment Value Curve

Man

agem

ent V

alue

for C

usto

mer

Integration Investment (Time and Resources)

1. Metric Instrumentation Low cost -- Immediate Value

2. Repository Integration Medium cost – Greater Value

3. UI Integration Higher cost – Most value

1

2

3

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!

Integration Points: Agent

Metric Engine

Collector Task Executor

Fetchlet 2Fetchlet 1 Fetchlet 3

Transfer

Java APIXMI

ConfigFile

TargetMetadata

CollectionDefinitions

V 1.2

Managed Target

Managed Targets

Preconfigured WBEM Enabled User Defined

V 1.1

EM Agent

Collector Metric Engine Presentation API Task Executor Etc...

Managed Target : Examples ..Managed Target : Examples ..

LOGINServer

BIG IPApp 1

DB 1

Backend

JS

JS

JS

JS

JS

JS

Apache 1

Apache 2

Middle Tier

Apache 3DB 2

V 1.1

Cisco Router

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)

Management RepositoryManagement Repository

Internal Table LevelInternal Table Level

Public “MGMT_” LevelPublic “MGMT_” Level

Application LevelApplication Level

Central Policy

Inventory

DB Config

Monitoring

ECM & APM

V 1.1

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.

Putting it all togetherManaged Targets

EM Daemon

XML

Target DefinitionFiles

XML

Metric DefinitionsMetric DataAlertsClient Response TimesWeb Server Response Times

Notifications

Firewall

HTTP(S)

InternetJune 2000

ReportingReal-time Monitoring

InformationRollup

Notification

V 1.3

ManagementRepository

Example: Simulation Engine Queues

SEES

EnterpriseServer

SE-Agent

AgentServer

SE-Server

Computation Server

...

SE-Agent

AgentServer

SE-Server

Computation Server

...

SE Client

Client host

How do I instrument my app ?• Separate the application into multiple targets,

and define them separately

• Determine what makes up the application: ComponentsAvailability Performance

Prerequisite

How do I instrument my app ?

• Define targets - pick your metric- compute metric

• Define collections- collection

schedule- Instantiate your

targets using the EM UI.

Declare the targets

Set thresholds

Define collections

Define target type

Workflow

How do I instrument my app ?

AgentEM SDK Provides

Predefined Collection Mechanisms: Fetchlets

Example Fetchlets: SQL and PL/SQL, SNMP, HTTP, Text,

WEBM…

Monitoring data immediately available

from EM Console

Define the targets you want to monitor and the

metrics you want to collect using XML

Targets.xmlCollections.xml

<targetname>.xml

Example : What makes up my app ?

Are my applications available?

Example: App specific metrics

Example: App specific metrics

Step 1: How do I define a target?

Step 2: How do I define collections ?

Step 3: How do I set thresholds ?

Step4: Declaring target instances

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 !

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

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

AQ&Q U E S T I O N SQ U E S T I O N SA N S W E R SA N S W E R S