INNOV-5: Web Services Management and Monitoring Daniel M. Foody Chief Technology Officer, Sonic.

INNOV-5: Web Services Management and Monitoring

Daniel M. FoodyChief Technology Officer, Sonic

© 2006 Progress Software Corporation2INNOV-5: Web Service Management and Monitoring

What you will take away…

How management is changing

What problems are solved by web services management (WSM)

How WSM applies to challenges you face


Agenda

Web service monitoring challenges Web service management challenges Introduction to the Actional™ architecture


Two kinds of monitoring to consider

Infrastructure monitoring• Is it up and running?

• What’s the CPU usage?

• How many threads are active?

Service monitoring• Who’s using the service?

• How is the service being used?

• Are we delivering adequate quality of service?


Anatomy of a monitored service

Above the water line All of the consumers (direct and

indirect) that depend on the service

At the water line The infrastructure the service is

directly built-on.

Below the water line All of the other services this one

depends on


“We think there are 5 applications using our service”

“We know we gave the WSDL to a couple of groups, but we think they’ve given it out.”

Monitoring above the water line: Case study

They thought wrong!!!34 apps used the service


Monitoring above the water line

Consumer requires6 seconds averageresponse time

Consumer requires8 seconds average

response time

Average response timeof service is 5 seconds

How do you know if consumers are happy?

You don’t, unless you measure on a per-consumer basis.


Monitoring below the water line

Just because it runs doesn’t mean it works Problems rarely appear at the root cause Sporadic failures are very difficult to find

Tim

e an

d c

ost

to f

ind

cau

se

Type of problem

Outage oravailability

Performancedegradation

Sporadic

Businessprocess notcompleting

Situational

Problem resolution is complicated with connected applications


Monitoring below the water line

There is a significant knowledge gap in production• Different people build apps than operate them

• Architecture diagrams are invariable out of date

Operations need accurate maps of actual application topology• For problem resolution, capacity planning, etc.

• Automate mapping of application topology– It’s always accurate, always up-to-date

Knowing what should be happening is not really knowing


Automatically discovers and maps out business processes, dependencies, and services

• Beyond XML and web services• Synchronous and asynchronous flows• Correlates flows through applications• Non intrusive• No configuration• Based on real activity

Dynamically segments, categorizes, and analyzes messages by business criteria

• By customer, region, plant, etc.• Using content and context of messages

Addressing the challenges with Actional

JDBC

HTTP

EJBDatabase

Legacy Application

Custom Data Source

Adapter

Packaged Application

App ServerPresentation

App ServerData / Service

Web Server

ESB, MQWeb Services


Looking from the eyes of IT and Business

By Infrastructure

• Which services are where?

• Who uses what services?

• Where are the bottlenecks?

• What’s the impact of change?

By Business Criteria

• How is my business doing?

• Are customer having issues?

• Am I keeping up with demand?

• Am I meeting my commitments?

By Business Process

ProductionProduction

PurchasingPurchasing

SalesSalesSalesOrder

DeliveryCustomer

Billing

PlannedOrder

ProductionOrder

PurchaseOrder

GoodsReceipt

• What really occurs in ordering?

• How many are in production?

• How long from order to delivery?

• Why has purchasing stalled?

Addressing the challenges with Actional


Monitoring Challenges addressed by Actional

How do I understand behavior and resolve issues?• Usage metering• Service level monitoring• Performance degradations• Activities not completing• Business exceptions• Security attacks

How do I ensure governance at runtime?• Detect rogue services and

unexpected service usage• Ensure security, compliance,

and other policies are enforced

JDBC

HTTP

EJBDatabase


Legacy Application

Custom Data Source

Adapter



Web Server

ESB, MQWeb Services


Agenda

Web service monitoring challenges Web service management challenges Introduction to the Actional architecture


Management vs. Monitoring

Monitoring is passive• “Your house is burning down”

Management is active• “We’ve turned the sprinkler system on”

Confusing because most “management” products, for the most part, only monitor


ESB, MQWeb Services

Management Challenges addressed by Actional

JDBC

HTTP

EJBDatabase

Web Server



Legacy Application

Custom Data Source

Adapter


“Are my business processes executing as expected for each customer, region, plant, etc.?”

“How do I route based on content or context?

How do I optimize routing for business value (e.g. reroute gold customers when close to SLA limit)?”

“How do I handle an overload of traffic, serving the most important uses first?”

“How do I bring online a new version without disrupting service?”

“How do I ensure security and compliance of my services?How do I achieve interoperability for my web services?”


Highlighting three management challenges

Policy enforcement• Security requirements• Sarbanes-Oxley• EU privacy regulations• HIPAA

Optimizing IT for the business• Give your most important customers the best service

Versioning• Maintenance windows are disappearing

Key goal: Factor these out of the application logic


Policies are driven top-down

Content Policies Process Policies Business Policies

ProductionProduction

PurchasingPurchasing

SalesSalesSalesOrder

DeliveryCustomer

Billing

PlannedOrder

ProductionOrder

PurchaseOrder

GoodsReceipt

Encrypt all personal identities for EU privacy compliance

Alert if the service level for a gold customer is close to the limit

Audit all messages that are part of a financial process for SOX compliance

<Licensee><ID>1837363</ID><Name>John Q. Public</Name><SSN>145-98-3847</SSN><Address><Street>100 Any Lane</Street><City>Any Town</City><State>CA</State><Zip>94099</Zip>

</Address></Licensee>

But, policies must eventually be enforced, somewhere, in the infrastructure


Optimizing IT for the business

IT capacity plans so that everyone can be treated equally under peak conditions• Leads to average utilization of 15%

Not everyone should be treated equally!• Different customer/regions/etc. have different

value to a business: IT must recognize this


Versioning services without downtime

Services have data. Data needs to migrate.• Before: All requests routed to v1

• Step 1: Reject change and route query to v1

• Step 2: Migrate data from v1 to v2 system

• Step 3: Route all requests to v2

consumer

v1service

v2service v2 DBv1 DB

Web Service Mgmt

Query Change

consumer

v1service

v2service v2 DBv1 DB

Web Service Mgmt

QueryChange

1

2

3

v1 DB

Registry Registry


Agenda

Web service monitoring challenges Web service management challenges Introduction to the Actional architecture


Enterprise Management

Identity ManagementDirectories

LookingGlassServer

Management Layer

Looking Glass™ in Action

Application Layer

Services FromExternal Sources

Services ToExternal Sources


Actional’s Patented “Flow Map” Technology




Management Layer

Business/User Layer

Application Layer



Architects

Developers

Business Users

Customers/Partners

IT Security

IT Operations

LookingGlassServer

Looking Glass in Action




Management Layer

Business/User Layer

Application Layer



Architects

Developers

Business Users

Customers/Partners

IT Security

IT Operations

LookingGlassServer

Looking Glass in Action


Actional products in the application layer

Visibility

Control

Ghost Agent

SOAPstation™

• Weightless, non-intrusive (microseconds of latency)• Web services, database, messaging, and more• End-to-end process visibility across applications• Automatic discovery, auditing, alerting, analysis, and reporting of service activity

• Runs standalone or in conjunction with Looking Glass• Policy enforcement (security, compliance, etc.)• Zero downtime service versioning• Adaptive content based routing, load balancing, and proactive fail-over for applications

Application Layer




In Summary

Factor out quickly-changing requirements• Regulatory compliance, etc.

Be proactive, not reactive• Reactive is no longer an option

Manage top-down• It’s the business stupid!


Questions?

For more information:• See Actional in the Expo• Go to http://www.actional.com


Thank you foryour time


INNOV-5: Web Services Management and Monitoring Daniel M. Foody Chief Technology Officer, Sonic.

Documents

monitoring monitoring

service slide

service monitoring whos

monitored service

infrastructure monitoring

monitoring daniel

kinds of monitoring

monitoring anatomy