WSReliability Interop

1
WS-Reliability Inter-op

• Now that we are done..
• November 18, 2004

2
WS-Reliability 1.1

• Oasis Standard as of November 15, 2004
• Result of an standards process open to all with
  contributions by
• Arjuna Technologies Limited, Booz Allen Hamilton,
  Choreology Ltd, Cyclone Commerce. France Telecom,
  Fujitsu, Hewlett-Packard, Hitachi, Ben Bloch,
  Mark Hansen, Paolo Romano, Mitre Corporation, NEC
  Corporation, Nokia, Novell, Oracle, SAP,
  SeeBeyond Technology Corporation, Sun
  Microsystems, University of Hong Kong, webMethods
  Inc., WRQ Inc.

3
Rationale for WS-Reliability

• Web Services increasing being utilized for
  operations that require transactional integrity.
• Unpredictable delay and multiple paths create
  havoc in complex applications with needs for
  coherent transmission of multiple messages.
• Thus, a normative mechanism that supports
  mission-critical Web Services applications

4
WS-Reliabilitys Primary Features

• Guaranteed Delivery
• Messages are persisted at sender until
  responsibility for message has been transferred
  to receiver.
• Duplicate Elimination
• Duplicates caused by re-tries (or lost
  acknowledgements) are eliminated
• Message Ordering and Grouping
• Association of multiple messages into an ordered
  sequence. Guarantees application receipt in
  correct order
• Support for Polled Status

5
Specification to Implementation

• During standards development
• Trial implementations
• Limited interoperability test
• After standard is created
• More complete implementation
• More extensive interoperability test
• Deployment in commercial systems

6
Business Grid Computing Project

• One of the first commercial uses of
  WS-Reliability
• Sponsored by the Ministry of Economy, Trade, and
  Industry of Japan
• Collaborative with the Grid Technology Research
  Center of AIST
• Industry members include Fujitsu, Hitachi, and
  NEC
• Approaching third and final year

7
Big Picture - how it works -

• Job Submission
• Standard job description and application contents
  service (using WS-Agreement protocol)
• Including self-healing -optimizing policies
• Brokering allocates necessary IT resources
• From physical resource pool
• Automatic deployment and configuration of program
  and data
• Includes necessary hosting environment
  preparation
• Resource Virtualization realized through grid
  Middleware agents which provide a common interface

Job Description
Business Application
AP Server
DBMS
Web Server
Automatic Resource Allocation
AP Server
Standard Resource Description
Business Applications
Provisioning Service
Logical Resource Pool
?????
Virtualization
Physical Resource Pool
8
Business Grid Standardization Map
OASIS
GGF

• Standardization of basic service interfaces,
  including protocols and schema, for each
  building block

GRAAP-WG JSDL-WG
Self-healing self-optimization Services
Disaster Recovery
Load Balancing
Fail-over
WSBPEL TC
Job Execution Management
Resource Management
System Configuration Management
Brokering
Job Manager
CMM-WG
Security
Deployment Mgmt
Workflow management
Job Restart management
Policy management
WSDM TC
Business Grid Middleware
WS-RM TC

• CDDLM-WG

Reliable Messaging
OGSI-WG
OGSI / WSRF
WSRF TC WSN TC
Hosting Environment

• OGSA-SEC-WG
• OGSA-AuthZ-WG

OS
9
Inter-op Demo Purpose

• Test interoperability in a mixed-vendor
  environment.
• Gain implementation experience.
• Feedback that experience to the technical
  committee.
• Promote the standard and demonstrate usefulness

10
Demo Configuration
Sender Test App
Receiver Test App
RMP2
RMP1
(WS-R node)

• Network
• trouble maker
• Message loss
• Message duplicates
• Message dis-ordering
• Ack loss

(WS-R node)
11
Demonstrations

• Guaranteed delivery
• Duplicate Elimination
• Message Ordering
• Composability with WS-S