Managing Web Services Effectively

1
Managing Web Services Effectively

• Cameron Haight
• 12 April 2004

2
An Evolutionary Oddity ...

• They lay eggs like a bird or a reptile
• They produce venom like a snake
• They have a bill and webbed feet like a duck
• They have fur and a tail like a beaver
• They produce milk and are mammals
• They are an endangered species found in niches

Duckbill Platypus Ornithorhynchus anatinus
By 2008, more than 90 of todays vendors
focusing on managing Web services will have
become extinct (0.9 probability).
3
Client Issues

• 1. What are the challenges in managingWeb
  services?
• 2. How is the vendor market evolving with respect
  to the management of Web services?
• 3. What steps can organizations take to improve
  their Web services delivery?

4
Client Issues

• 1. What are the challenges in managingWeb
  services?
• 2. How is the vendor market evolving with respect
  to the management of Web services?
• 3. What steps can organizations take to improve
  their Web services delivery?

5
Sidestepping the Potholes Challenges to the
Management of Web Services
3
1
Technology
Standards
Infrastructure

• XML/SOAP impact
• Dynamic binding
• Loosely coupled

• WSDM not finalized
• Security and other dependencies
• Integration with JMX, CIM ...

• Application stack dependencies
• Web services components
• .NET and J2EE

4
Vendors

• Product approaches
• Lack of compatibility
• Vendor viability

Process
Path to Success

• Life cycle support
• Limited instrumentation
• Change management

5
Organization

• Internal ownership
• Interenterprise
• Skills maturity

6
The Web Services Layer Doesnt Stand Alone

• Not sufficient to just monitor Web services layer
• Component health
• SOAP engines, UDDI directories ...
• Service levels
• Need to monitor interdependencies
• Business processes
• Supporting infrastructure

BP
BP
BP
Web Services
Servlet
MQPut
SOAP
JMS
MDB
Network System Database Storage
Impact Require integrated toolset not just
point product solutions
7
XML Hot SpotsAffecting the Performance of Web
Services
De- serialization (XML to Java)
Parser (and validation)
XML Document

• CPU impact
• Parsing (symbol identification)
• Transformation serialization/de-serialization
  (object marshalling ...)
• Network impact
• XML can be 5 to 20 times the size of binary data
  streams

Application Code
Serialization (Java to XML)
XML Document
Impact Drive demand for testing and capacity
planning/modeling tools, as well as XML appliances
Source Diagram adapted from IBM/Actional
material.
8
Management StandardizationAnother Set of
Dependencies
Related Initiatives
Netconference Config. Protocol (July 2003)
ARM ARM 1.0 (1996)
OASIS WS-Classic WS-Security/WAS SPML
Pre-OASIS
OASIS
DMTF CIM-XML (1998) CIM-SOAP (2003)
IBM/CA/TB WS-Manageability (September 2003)
HP WSMF (July 2003) WSRF (February 2004)
WS-I Basic Profile (February 2002)
OGSA Common Management Model (July 2003)
W3C/MTF WS Endpoint Management Architecture (2003)
MPTC (July 2002)
WSDM (February 2003)
HP/ webMethods Open Mgmt. Interface (2001)
Vendors WS-Policy (BEA, IBM, Microsoft, SAP, May
2003) WSLA (IBM, January 2003)
Mgmt. Protocol Spec
MOWS (May 2003)
MUWS (May 2003)
Management Data Models
SNMP
JMX
CIM
Continuing Influence
9
Todays Management MarketMuch Obfuscation and
Little Integration
Content-Based Routing
Service- Level Management
Data Transformation
Extranet Access Management
Management of Web Services Offerings
EAI Buyer
ESM Buyer
Business Process Monitoring
Legacy Integration
Application Development
Enterprise Console Integration
10
Organizational Ownership andProcess Scenario
(IT) Service-oriented
Line of Business
Infrastructure skills
Operations processes
Management architecture
SLA Impact
Business-oriented
Service monitoring
Web services skills
Development processes
Integration architecture
Service orchestration
End-to-end management gap
11
Client Issues

• 1. What are the challenges in managingWeb
  services?
• 2. How is the vendor market evolving with respect
  to the management of Web services?
• 3. What steps can organizations take to improve
  their Web services delivery?

12
Managing Web ServicesA New Vendor Taxonomy
Enterprise Service Bus
Enterprise Systems Management
Web Services Middleware
Development
Integration
Management
Web Services Broker
Multiprotocol ESB
Web Services Controller
Web Services Application Manager

• Fiorano Software's ESB
• IBM's Services Integration Bus (a future product)
• IONA Technologies' Artix
• Kenamea's Web Messaging Platform
• KnowNow's Event Routing Platform
• Microsoft's Indigo (a future product)
• PolarLake's JIntegrator
• Software AG's EntireX
• Sonic Software's ESB
• SpiritSoft's Spiritwave
• WebV2's Process Coupler

• Actional
• AmberPoint
• Oblix (Confluent)
• Hewlett-Packard/ Talking Blocks
• Infravio
• Itellix

• Computer Associates (Adjoin)
• Hewlett-Packard/ Openview
• Reactivity
• Service Integrity
• Westbridge

• Blue Titan's Network Director
• Cape Clear's 4 Server
• Digital Evolution's DE Management Server
• Flamenco Networks
• Primordial's Web Services Network
• Systinet's Web Services Bus
• webMethods' Fabric

13
Today Market EmergenceTomorrow Market
Obliteration

• 2003-2004A market is born and begins to
  perish!

CA
Adjoin
Talking Blocks
HP
Confluent
Oblix

• Life cycle transition
• Vendor capitalization

Interlude Continuing market tectonics

• Different buying centers
• Best of breed
• Overlapping function

2008 Zero entropy natural order resumes
Management
Integration
14
Web Services DevelopmentThe Beginning of
Real-Time Infrastructures?
Development
Production
Security Mgmt. Policy
Control
Service Notification
2
Service Alert
Web Services Provider
Control
Web Services Consumer
Web Services Provider
Service Adjustment
Web Services Infrastructure
Example vendors Actional and AmberPoint
Pros
Cons

• Management flexibility
• More precise control of management policy
• Development involvement

• Need source code (no packaged applications)
• Increased application complexity
• Vendor lock-in

15
A Management Niche XML Appliances
Goal Offload server resource impact
Application Server
Database
XML Proxy
TRaX API (JAXP)


1




Voice
2
XML Relay
Web Servers
Transformation Compression Caching Encryption
PDAs
PCs
Example vendors DataPower, Sarvega and Forum
Systems
Goal Reduce network infrastructure impact
PCs
16
IntermediationXML Management Techniques
Advantages
Disadvantages
Agents

• Leverage infrastructure
• No extra hop processing

• Require per-Web services node
• Potential platform resource impact

Methods SOAP engine plug-in, NSAPI/ISAPI filter,
Servlet redirection
Hosted
Management Server

• Supports many Web services nodes
• .NET and J2EE support

• Single point of failure
• Additional hop processing delays

Policies Stats
Methods Stand-alone server client-side proxies
available for debugging ...
SNMP
XML
Proxy
Management Console
ESM Infrastructure

• Supports many Web services nodes
• No impact to service performance

• No active capabilities
• Cannot see intra-node sessions

Methods Attaches to network device (switch ...)
Network
17
A Closer Look SOAP Plug-Ins
.NET ASP.NET SOAP Extensions
Management Agent

• Logging
• Monitoring

De- compress
Access Control
Decrypt
Mgmt.
Transform
Service Interface
Service Implemen- tation
Access Control
Encrypt
Compress
Mgmt.
Transform

• Metering
• Billing

SOAP Handlers
J2EE JAX-RPC API
18
Client Issues

• 1. What are the challenges in managingWeb
  services?
• 2. How is the vendor market evolving with respect
  to the management of Web services?
• 3. What steps can organizations take to improve
  their Web services delivery?

19
Web Services GovernanceThinking Through the
Issues
How do we address our IT issues using Web
services? Who is responsible for developing,
executing and managing ourorganizations Web
services? Who pays for Web services?
What are our SLAs? What are our security
requirements? What are our management
requirements?
CTO CSO CFO
Integration Competency Center Systems
Administrators Security Administrators
What are the requirements for our Web services
framework?
IT Project Managers Applications
Developers Systems Administrators
Do we outsource to a WSN?
What are our requirements for Web services
middleware?
20
Web Services DeliveryCoordinate Process
Execution (or Fail)
Integrated Process Teams
Architecture Standards
QA
Application Development
Operations
Service Partner
Application Design
Event and Performance Management
Service-Level Management
Change Management
Process Automation
21
A Maturity Model for ManagingWeb Services
Level 4
Value
Level 3

• IT and business metric linkage
• IT improves business process
• Real-time infrastructure
• Business planning

Service
Level 2

• Define services, classes, pricing
• Understand costs
• Set quality goals
• Guarantee SLAs
• Monitor and report on services
• Capacity planning

Proactive
Level 1

• Monitor performance
• Analyze trends
• Set thresholds
• Predict problems
• Automation
• Mature problem, asset and change mgmt. processes

Reactive
Level 0

• Best effort
• Fight fires
• Inventory
• Initiate problem mgmt. process
• Alert and event mgmt.
• Monitor availability (u/d)

Chaotic

• Ad hoc
• Undocumented
• Unpredictable
• Multiple help desks
• Minimal IToperations
• User call notification

22
A Future Scenario Service-Oriented Management
Architectures
SODA
Enterprise
Management ISV
Operations
Development

• Provide SOAP interfaces for data repositories
• Expose functions (i.e., SLM, trouble ticketing,
  policy mgmt.) as services using WSDL and UDDI
  (WSDM)

• Assemble management services (in-house and
  vendor-developed)
• Orchestrate/define management process execution
  order
• Expose management information to federated
  partners via Web services APIs (WSDM)

• Develop reusable management services (i.e.,
  logging)
• Expose management information via Web services
  APIs ensure separation of management operations
  from business operations
• Migrate to WSDM standards
• Create repository of reusable management services

Infrastructure ISV

• Provide Web services API separate management
  operations from business operations
• Migrate to WSDM standards

SOMA
23
Vendor ProfileManaging Microsoft MapPoint
MapPoint at a Glance 170 active customers 15
million transactions per day Transmit 250GB of
data per day

• Has achieved a very high-performance and
  availability record
• To meet future demands, looked for tools to
  augment management portfolio
• CA Unicenter WSDM provides in-depth transaction
  datastream analysis
• Keys to Web services success operations and
  development partnership

Customers (Starbucks, Verizon, Dominos Pizza,
etc.)
Management
Front End

• Availability monitoring (Mercury SiteScope)
• Performance monitoring (Microsoft MOM)
• User monitoring (KeyNote)

Web Services Interfaces
Production
Mapping
Find
Route
Database Servers (transaction logging, map data,
points of information, security)

• Diagnostics (CA Unicenter WSDM)

Extranet-based administration servers (account
mgmt., data uploading, reporting )
Test

• QA (Microsoft ACT)

Back End
24
Recommendations

• Get involved in the standardization efforts for
  Web services management
• Deploy tools that provide end-to-end and
  top-to-bottom management visibility
• Develop backup plans to isolate yourself from
  continuing market and vendor fluctuations
• Begin collaborating with internal IT and external
  partners on management processes
• SOMA will only happen if you demand it start
  requiring this in future requests for proposals