11
WS-Reliability Inter- op Now that we are done.. November 18, 2004

WS-Reliability Inter-op Now that we are done.. November 18, 2004

Embed Size (px)

Citation preview

Page 1: WS-Reliability Inter-op Now that we are done.. November 18, 2004

WS-Reliability Inter-op

Now that we are done..

November 18, 2004

Page 2: WS-Reliability Inter-op Now that we are done.. November 18, 2004

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.

Page 3: WS-Reliability Inter-op Now that we are done.. November 18, 2004

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

Page 4: WS-Reliability Inter-op Now that we are done.. November 18, 2004

WS-Reliability’s 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

Page 5: WS-Reliability Inter-op Now that we are done.. November 18, 2004

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

Page 6: WS-Reliability Inter-op Now that we are done.. November 18, 2004

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

Page 7: WS-Reliability Inter-op Now that we are done.. November 18, 2004

「仮想化」

Business Application

Web ServerDBMS

AP Server

AP Server

Business ApplicationsProvisioning

Service

Physical Resource Pool

Job Description

AutomaticResource Allocation

AutomaticResource Allocation

VirtualizationVirtualization

Logical Resource Pool

StandardResource

Description

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

Page 8: WS-Reliability Inter-op Now that we are done.. November 18, 2004

Business Grid Standardization Map• Standardization of basic service interfaces, including

protocols and schema, for each building block

Self-healing & self-optimization Services

Job Execution ManagementResource ManagementSystemConfigurationManagement

Deployment Mgmt

Policy management

Brokering

ConfigurationInformation

Business GridMiddleware

Job Manager

Workflow management

Job Restart management

Disaster Recovery Load Balancing Fail-over

OGSI / WSRF

Hosting Environment

OS

Secu

rity

Reliable Messaging

CMM-WG

WS-RM TC

GRAAP-WGJSDL-WG

• CDDLM-WG

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

OGSI-WG

WSBPEL TC

WSDM TC

WSRF TCWSN TC

GGF

OASIS

Page 9: WS-Reliability Inter-op Now that we are done.. November 18, 2004

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

Page 10: WS-Reliability Inter-op Now that we are done.. November 18, 2004

RMP2RMP1

Sender Test App

Receiver Test App

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

(WS-R node) (WS-R node)

Demo Configuration

Page 11: WS-Reliability Inter-op Now that we are done.. November 18, 2004

Demonstrations

• Guaranteed delivery

• Duplicate Elimination

• Message Ordering

• Composability with WS-S