how to leverage ibm technology and custom portal dashboards to monitor the health and availability...

CONNECT WITH US:IT: Customized to Your Advantage

Monitoring an Enterprise Service BusMonitoring Best Practices

SURESH WILSON

Public | Copyright © 2014 Prolifics

http://www.youtube.com/prolificstv

http://www.linkedin.com/company/prolifics

http://www.facebook.com/prolificstech

http://twitter.com/prolifics/

CONNECT WITH US:Public | Copyright © 2014 Prolifics

Agenda How to monitor an ESB?

Which components to monitor?

How to provide better visibility?

Better notification and problem determination

Agent best practices

Reporting

WSRR Integration for policy monitoring

2






A Typical ESB

DB2 Database

Legacy Systems

DataPower

DataPower

MQ

MQ

IIB (WMB)

IIB (WMB)WS Providers

ServIce

Consumers

3






How to monitor an ESB?

Use Monitoring tools

Preferably a single tool that can monitor all the ESB components

consolidated viewcentralized monitoring and alertscommon reporting

4






Typical ESB Monitoring needs

Development cycle•Understand application behaviour

•Diagnose and fix problems

•Replay production failures and help fix problems

Test cycle•Understand and isolate connectivity issues and source of problems


Performance cycle•Measure and report performance behaviour

•Assist in infrastructure sizing

•Optimize application and system performance

Production cycle•Help ensure continuous availability and measure performance

•Real time monitoring and automate response actions

•Report usage statistics and help in capacity planning

5





CONNECT WITH US: 6Public | Copyright © 2014 Prolifics

Typical Challenges with ESB Monitoring

Multiple components

Too many data points

Correlating data

Tracking the service flow

Provide meaningful views






Non-technical challenges

Monitoring teams and applications teams typically do not work together

Applications teams do not know the capabilities of the monitoring tools and the monitoring teams do not know what the application teams need

• Identify key members and have them work together to put together the best possible solution

7







8







Monitor everything that makes up the enterprise bus

• Front end (Web servers, appliances etc.)• Business logic layer (IIB, BPM etc.)• Messaging layer (MQ etc.)• Databases• Operating systems• Legacy sources

9






Why?

Any participating product or component can contribute to the reliability (or lack thereof) of the ESB

Monitoring each component is essential to proactive availability and health monitoring

Don’t let unknowns cause surprises

10






The Tivoli (C&SI) Way

11






Tivoli - For all the monitoring needs

Development cycle•Understand application behaviour


•Replay production failures and help fix problems

Test cycle•Understand and isolate connectivity issues and source of problems


Performance cycle•Measure and report performance behaviour

•Assist in capacity planning and environment sizing

•Optimize application and system performance

Production cycle•Help ensure continuous availability and measure performance

•Real time monitoring and automate response actions

•Report usage statistics and help in capacity planning

12






Why Tivoli/ITCAM?

Agents and capabilities to monitor (almost) every market leading product

Integration between the various products (WSRR, TBSM, JazzSM, Omnibus etc.)

Unified, customizable and extensible interface

Built on the solid Tivoli Monitoring Foundation

13






Why Tivoli/ITCAM - continued

Monitoring, automation and reporting capabilities for

service performance application servers messaging infrastructure virtual environments operating systems so on and on

Use these to quickly identify and isolate problem areas

14






Example – SOA Aggregate views

See how the service requests flow through the various components

• Helps to easily identify bottlenecks, problem areas

15







16







Understand the environment from an application and services perspective

Identify the critical areas (Queues, Channels, DataPower objects, Message flows, Applications, CPU, Disk I/O etc.)

Build custom dashboards to display the various components that participate in a service

17






Work with the consumers

Consumers (developers/ administrators/ business users etc.)

Understand what they want to see

Understand how they want to see it

Increase the return on investment by leveraging the data provided by the agents

18






Create user-friendly easy to use dashboards

From the default views to…

19






Example Dashboard – Custom views

…easy to understand dashboards

20






Create consolidated dashboards

21






Example Dashboard – OS Level

22






Example Dashboard – MQ Status

23






Example – DataPower Status from multiple appliances

24






Example – Service Provider Status Dashboard

25






Example– Dashboard For Operations Team

26






Notifications

Use the out-of-the-box situations when it makes sense

Start with the numbers seen during performance testing

Fine tune the situations on a regular basis

Too many alerts is as good as no alerts

27






Agent Best Practices

Know the agent behavior in your environment (product version support, performance behavior etc.)• Not just OOTB, but also for environment specific requirements

Start with the development environment – no after thought – be proactive

Routinely implement updated configuration as the solution matures

28






Agent Performance

Agents do have overhead; understand the numbers

Plan for the overhead during infrastructure sizing

Performance Testing – not just for the application, also for the agents and the Tivoli infrastructure(agent level, TEMS-TEPS level, DWH level)

29






Reporting

30






Reporting

Use Tivoli Common Reporting• Easy to understand graphical reports• Use for usage statistics, trend analysis etc.

Build custom reports for environment specific reporting requirements

31






Sample List of Reports

32






Sample OS Report

33






ITCAM for SOA - WSRR Integration

34






ITCAM for SOA – WSRR Integration

Author the service policies in WSRR

Enforce the policies in the Runtime (DataPower/IIB/BPM)

Monitor the policies using Tivoli

Automatic propagation of policies from WSRR to Tivoli

35






Create a WSRR policy

36






Provide the policy details

37






Provide the policy details

38






Attach the policy to the SLD

39






Tivoli monitors the new policy

40






Meeting the monitoring goals

Know about the end user experience

Help understand root causes

Measure performance behaviour

Report on usage and assist in capacity planning

Help tune and optimize performance

Trigger proactive notification alerts

41






Thank You

42





how to leverage ibm technology and custom portal dashboards to monitor the health and availability...

Technology