Application Management

Peter WilliamsManaging ConsultantOV Solutions TeamHewlett-Packard Company

Session Topics...

• Instrumenting your applications• Threshold management• Reporting• Event management integration

Tivoli and

Boole & Babbage Compuware,HP Open Mail, Net

Version 1.0 of the ARM API was announced in June 1996 byHewlett Packard.Companies initially endorsing the ARM API:

, Candle,Systems, NCR, Netscape, Platinum Technology, SAS, SunMicrosystems, Sybase, Texas Instruments, Unify and the ComputerMeasurement Group

ARM Working Group formed in December of 1996 and releasedVersion 2.0 in December of 1997

Background of ARM

Tivoli TME Program

HP OpenView Program

An Open APIOpen Industry LicensingVersion 1.0 and 2.0

•10/Plus Association

•Application Management Specification

•TME 10 Products (Response Time Agent)

•HP OpenView Partners

•HP OpenView APIs

•HP OpenView Products

(HP MeasureWare)

HP Openview Program

Tivoli Corporation

Version 1.0

ARM Working Group

Version 2.0

Distributed architectures create challenges for end-to-end management

Mainframe System

Elapsed Time

Data from One Business Transaction is typically fully contained

ClientsApplication

ServerDatabase

Server

Network Network

Elapsed Time

Client Network AppServer

Network DBServer

Data from One Business Transaction is not fully contained

Centralized Environment Client-Server Distributed Environment

Network

Terminals

Key problems that ARM helps to solve for end to end application management:

Is the application hung? What level of response time are the

application users experiencing? Where are the bottlenecks occurring

during my application execution? Who uses the application? Which

transactions? How much? How can my application be tuned to

run better in my environment?

ARM API Software Development Kit Version 2.0 is now -Available-

Common API

Dev. Library

Developer KitDeveloper Kit

ARMAPI

Specification for the API Source code included to allow

extensions Provides for multi-vendor

environment Provides for prevalent

programming languages

Development Libraries Allows compile without installation

of management product

Application developers can get started to instrument applications

Covers wide range of UNIX systems and PC-based systems

Sample Logging Agent

arm_init identifies applications/user_id and initializesarm_getid registers a transaction by namearm_start indicates the start of a unit of workarm_update shows progress and status (optional)arm_stop indicates the end of a unit of workarm_end disables the environment for this application

Standard C language bindings, but libraries are language-neutral(Samples for COBOL, Visual Basic, Pascal)

Six API Calls

What does the API look like?

Application Development

Program Source Code

ARM SDKComponent

DevelopmentLibraries

Transaction 1 Start

Transaction 2 Start | | |Transaction 2 Stop

Transaction 1 Stop

CompileManagementReady Application

ARM API CALLS

Management of the Application

Application Example

sManufacturing Apps.Financial ApplicationsRetail Applications

Start

Stop

Application

Monitor

Agent

Management

ApplicationReal-Time Performance Analysis and Event Notification

Log

Historical DataReports

ARMAPI

BusinessApplications

Navigation Tree

Events

Note

Browser

James Hill working 13 Jan 10:30am

Critical

Major

Minor

Warning

Cleared

Mon Jan 13 10:13:11 swango.ral

Topology View

Topology View

Events

Control Desk

Event History

Mail

CPU Perf

SNMP Errors

Events

LMU/6000

Tools

Highlight

STOP

START

CLIENTS

ARMAGENT

STOP

START

ARM APILib.

ARMAGENT

LOGFILE

ARM APILib.

Network

SERVERS

BusinessApplications

Management Applications

Management Database

LOGFILE

APPLICABLE THRESHOLDS:- Transaction count/rate- Transaction failures, hangs

START received but no STOP, orTransaction Status = ERROR

SERVER 2

Scenario: Availability (hung/failed txn)Set thresholdsControl loggingGraph dataGraph recent historyView transactions in process

AGENTARM

Process Events

CONFIG FILE

Event ManagementApplication

RealtimeMonitoringApplication SERVER 1

START

CLIENT

NETWORK

Scenario: Service Level & Workload Tracking

SeqFile

SQL

ReportingApplication

DailyUploads

Reports trends exceptions

AGENTARM

Note: ARM Agent also monitors servers

RealtimeMonitoringApplication

Control: - Collections- Logging

CONFIG FILE

STOP

SERVER 1

SERVER 2

START

CLIENT

NETWORK

Response Timeaverage,max/minStatistical

distributionTransactions

totalnumber good/bad

Exceptionsfailures, hangs

lkhglkl;fladfjglh;glladfjljdfjgkfdjglkdjflgkljfgliirkjreopijaf

Scenario: Response Time ProblemSet thresholdsControl loggingGraph dataGraph recent history

Event ManagementApplication

AGENTARM

Process Events

APPLICABLE THRESHOLDS:- Response time: average, max/min, distribution, any transaction- Transaction count/rate- Transaction failures, hangs

Note: ARM Agent also monitors servers

CONFIG FILE

RealtimeMonitoringApplication

STOP

SERVER 1

SERVER 2

START

CLIENT

NETWORK

Measurements From a Typical ARM Solution

Heartbeats from long running transactions– count of heartbeats since beginning of transaction– times of first and last heartbeat

Detection of Hung or Failed Transactions– time each transaction started– last completed transaction– optional threshold alarm if taking too long

Response Times – average, maximum, minimum – statistical distribution (seven "buckets")– per interval over the last several intervals, or– last completed transaction

Transaction Counts/Rates – total number of attempts– total good, failed, aborted

ARM Working Group Mission Statement

“ The purpose of the ARM API is to enable applications to provide information to ensure business transactions from an end user perspective and the contributing components of response time in distributed applications. This information can be used to support service level agreements and to analyze response time across distributed systems.”

ARM 2.0 Enhancements

Provides sample logging agent for testing purposes with instrumented code

Passing of simple application-specific measurements via simple counters, gauges, and strings to support response time context troubleshooting

Enables additional granularity of response time by decomposition of end-to-end response time into times for the major sub-componentsvia correlation of transaction id’s

Client-Server ApplicationEnd to End Response Time Measurement

Transaction End to End Response Time

arm_initarm_getidarm_startarm_endarm_stop

Client WorkstationsWin. 3.x, 95, NT, Un*x etc.

Application ServersNT, Un*x etc.

Database ServersNT, Un*x etc.

Client-Server ApplicationEnd to End Response Time Measurement (2)

Transaction End to End Response Time

arm_initarm_getidarm_startarm_endarm_stop

Client WorkstationsWin. 3.x, 95, NT, Un*x etc.

Application ServersNT, Un*x etc.

Database ServersNT, Un*x etc.

arm_initarm_getidarm_startarm_endarm_stop

arm_init, arm_getid,arm_start, arm_end,arm_stop

Application Server Response Time

DB Server Response Time

Client-ServerResponse Time Breakdown

0

20

40

60

80

100

Client Resp. Time

App. Svr. Resp.TimeDB Svr. Resp.Time

"Binding Measurements to a Transaction Instance"

Transaction Measurements

Transactions Measurements

ARM 1.0

Transactions Measurements

ARM 2.0

Measurements

Service Reporter Quick View

Database Server

Application Server

Web Server

Network

HP MeasureWare Distributed IT environment

collecttime stamplogalarm

HP OpenView Central management console

SLA

ITP

lann

ing

LOBIT

web browser

Reports

Service Reporter

Which resources?What reports?How often?

Service Reporter Block Diagram

MeasureWareAgents

(No Modification)

Central Reporting System

CentralReportingDatabase

Reports

MetricLists

ReportTemplates

ReportConfig

Web Page

User Interface

GathererEngine

Discovery ReportEngine

MasterScheduler

MetricSelector

Maintenance

Service Reporter Web PageOut of the Box Reporting

Service ReporterExample ARM Transactions Report

Service ReporterExample Service Level Report

Service ReporterExample Busiest CPUs Report

More detailed information about these systems is provided -- just scroll down the window!

Service Reporter

SMART Plug-Ins

• SMART Plug-Ins are not discrete management tools

• Use existing HP OpenView User Interface, management server, and agent infrastructure

• Full process integration, e.g. pre-configured message grouping, application bank, node bank

One platform to manage networks, systems, middleware, databases and applications!

ManageX AgentITO AgentUnix & NT

MW AgentUnix & NT

HP OpenView SMART Plug-InsPositioning Within OpenView Family

Application “XXX” Application “XXX”

IT/O Console PerfView ManageX Console

Management Server

Managed Node

ManageX

ServiceNavigator

ServiceReporter

ManagedNode

ManagementServer

Message Browser

ITO GUIApp Bank PerfView

Process, NOS,Desktop, Nerf,Oracle, SAP R/3,Informix, etc.

SPI Architecture - ITO/MWA

MessagePolicies

(SPI)

AnalysisPolicies

(SPI)Collector

(SPI)

Log/Event FilePolicies (SPI)

CommandLibrary(SPI)

ApplicationError/Audit

Logfiles

ApplicationTools

ApplicationProcesses,

Tables, MIBs

Application Instance

IT/OAction Agent

IT/OMsg Agent

MeasureWareAgent +DSI

IT/O LogfileEncapsulator

IT/O MessageInterceptor

IT/O MonitorAnalyser/Agent