INNOV5: Web Services Management and Monitoring

1
INNOV-5 Web Services Management and Monitoring
Daniel M. Foody
Chief Technology Officer, Sonic
2
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

3
Agenda

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

4
Two kinds of monitoring to consider

• Infrastructure monitoring
• Is it up and running?
• Whats the CPU usage?
• How many threads are active?
• Service monitoring
• Whos using the service?
• How is the service being used?
• Are we delivering adequate quality of service?

5
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

6
Monitoring above the water line Case study

• We think there are 5 applications using our
  service
• We know we gave the WSDL to a couple of groups,
  but we think theyve given it out.

7
Monitoring above the water line
How do you know if consumers are happy?
Consumer requires 8 seconds average response time
Consumer requires 6 seconds average response time
Average response time of service is 5 seconds

• You dont, unless you measure on a per-consumer
  basis.

8
Monitoring below the water line
Problem resolution is complicated with connected
applications

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

Sporadic
Situational
Performance degradation
Time and cost to find cause
Business process not completing
Outage or availability
Type of problem
9
Monitoring below the water line
Knowing what should be happening is not really
knowing

• 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
• Its always accurate, always up-to-date

10
Addressing the challenges with Actional

• 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

HTTP
EJB
JDBC
Custom Data Source
11
Looking from the eyes of IT and Business
Addressing the challenges with Actional
12
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

HTTP
EJB
JDBC
Custom Data Source
13
Agenda

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

14
Management vs. Monitoring

• Monitoring is passive
• Your house is burning down
• Management is active
• Weve turned the sprinkler system on
• Confusing because most management products, for
  the most part, only monitor

15
Management Challenges addressed by Actional
HTTP
EJB
JDBC
Custom Data Source
16
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

17
Policies are driven top-down
Content Policies
Process Policies
Business Policies
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
But, policies must eventually be enforced,
somewhere, in the infrastructure
18
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

19
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

20
Agenda

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

21
Looking Glass in Action
22
Actionals Patented Flow Map Technology
23
Looking Glass in Action
Customers/ Partners
Business Users
Developers
IT Security
Architects
IT Operations
Business/User Layer
Enterprise Management
LookingGlassServer
Identity Management
Directories
Management Layer
Services To External Sources
Services From External Sources
Application Layer
24
Looking Glass in Action
Customers/ Partners
Business Users
Developers
IT Security
Architects
IT Operations
Business/User Layer
Enterprise Management
LookingGlassServer
Identity Management
Directories
Management Layer
Services To External Sources
Services From External Sources
Application Layer
25
Actional products in the application layer
Ghost Agent
Visibility

• 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

SOAPstation
Control

• 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

Services To External Sources
Services From External Sources
Application Layer
26
In Summary

• Factor out quickly-changing requirements
• Regulatory compliance, etc.
• Be proactive, not reactive
• Reactive is no longer an option
• Manage top-down
• Its the business stupid!

27
Questions?

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

28
Thank you foryour time
29
(No Transcript)