Dr. Daniel Sabbah Vice President of Strategy & Technology IBM Software Group Bringing Grid & Web Services Together Globus World San Francisco, CA Tuesday,

Dr. Daniel SabbahVice President of Strategy & TechnologyIBM Software Group

Bringing Grid & Web Services TogetherGlobus World

San Francisco, CATuesday, January 20th, 2004

© 2004 IBM Corporation 2

Web Services

Business integration

Secure and universal access

Applications on demand

Grid Protocols

Vast resourcescalability

Global Accessibility

Resourceson demand

access manageshare

The Best of Both WorldsWeb Services & Grid Requirements


What we are announcing today Proposals to extend to Web services

Driven by requirements from:• Grid computing• Systems Management• Business computing

Key to infrastructure for IBMs On Demand Initiative

GridComputing

SystemsManagement

BusinessComputing

WebServicesbu

siness

on de

mand


Why we developed these proposals• To have an architecture that is more clearly

aligned with the general evolution of Web services

• To provide a collection of related specifications that can be used either individually or in combinations…

…. and will integrate more effectively with other Web services standards

• To more closely align with existing language and platform programming models and application development tools

What we are announcing today


A family of Web services specification proposals

• Introduces a design pattern to specify how to use Web services to access “stateful” components

• Introduce message based publish-subscribe to Web services

WS-

Serv

ice

Gro

up

WS-RenewableReferences

WS-

Not

ifica

tion

Modeling Stateful

Resources with Web Services

WS-B

ase Faults

WS-ResourceProperties W

S-Resource

Lifetime

IntroducedToday

To be developed



WS-Notification• Provides a publish-subscribe messaging capability

for Web Services

WS-Resource framework• A family of Web services specifications that clarify how

“state” and Web services combine

Both: • Build upon existing Web services specifications and

technology• Help align Grid computing, Systems Management

and Web services

Contributed to by:WS-Resource Framework: IBM, Globus, HPWS-Notification: IBM, Globus, Akamai, HP, SAP, Tibco,

Sonic



•OGSA Services can be defined and implemented asWeb services

•OSGA can take advantage of other Web services standards

•OGSA can be implemented using standard Web services development tools

•Grid applications will NOT require special Web services infrastructure

Network

OGSA Enabled

Storage

OGSA Enabled

Servers

OGSA Enabled

Messaging

OGSA Enabled

Directory

OGSA EnabledFile

Systems

OGSA Enabled

Database

OGSA EnabledWorkflo

w

OGSA Enabled

Security

OGSA Enabled

Web Services

WS-Resource Framework & WS-Notification are an evolution of OGSI

OGSI – Open Grid Services Infrastructure

How these proposals relate to OGSA

Web Services

OGSA Architected Services

Applications

WS-

Serv

ice

Gro

up

WS-RenewableReferences

WS-

Not

ifica

tion

Modeling Stateful

Resources with Web Services

WS-B

ase Faults

WS-ResourceProperties W

S-Resource

Lifetime


Service Composition

Transports

Messaging

Description

Quality ofExperience(QoX)

HTTP/HTTPS SMTP RMI / IIOP

XSD WSDL

SOAPXML WS-Addressing WS-Renewable References

WS-Metadata ExchangeWS-Policy

WS-Service Group

WS-Resource Properties

JMS

WS-Security

WS-Reliable Messaging WS-Transaction

WS-Resource Lifetime

WS-Base Faults

WS-Notification BPEL4WS

How these proposals relates to other Web services standards:


WS-Resource Framework CapabilitiesSpecifies how to use XML to describe and access a

resource’s properties

Clarifies how stateful resources are addressed

Defines how a resource is created and messages to destroy resources

Provides a message subscription and notification mechanism for Web services

Outlines how to organize groups of resources and services Adds a fault tolerance capability to WS-Addressing Defines a standard, extensible format for Web services error

messages


Web Services and Stateful Resources “State” appears in almost all applications

• Data in a purchase order• Current usage agreement for resources on a grid• Metrics associated with work load on a Web server

There are many possible ways Web services might model, access and manage state

• The WS-Resource framework proposes to standardize this capability for Web services


Inte

rface

WebService

The WS-Resource framework model

Web Service

WSDLRun-time environment


Inte

rface

WebService

message

message

Invoking a Web Service

address

Endpoint Reference

Run-time environment



What is a WS-Resource

• Examples of WS-Resources: – Physical entities (e.g.. processor, communication link, disk drive)

or Logical construct (e.g.. agreement, running task, subscription)

– Real or virtual

– Static (long-lived, pre-existing) orDynamic (created and destroyed as needed)

– Simple (one), or Compound (collection)

• Unique - Has a distinguishable identity and lifetime

• Stateful - Maintains a specific state that can be materialized using XML

• May be accessed through one or more Web Services

resource



context

Inte

rface

WebService

messageid

message

Using a Web service to access a WS-Resource

id

address

resource


Endpoint Reference



context

Inte

rface

WebService

messageid

message

Using a Web service to access a WS-Resource

id

address

resource

resource

Endpoint ReferenceEndpoint Reference




Inte

rface

WebService

message

message

Creating / Locating a WS-Resource

address

Endpoint Reference

resource

Endpoint Reference

Web Service either locates or creates a

WS-Resource

address

id




IBM

WS-Resource Properties• Resource state and metadata

“Projected” as an XML document• Query and Set operations

WS-Resource LifeTime• Explicit destruction or

“Soft state” time-to-live • Provides for cleanup

of resource instancesresource

<ProcessorProperties><ProcID>5A34C1DE03</ProcID><ProcArchitecture>Power6.2</ProcArchitecture><ProcSpeedMIPS>400</ProcSpeed><ProcCacheMB>256<ProcCache><ProcRunning>1</ProcRunning>

</ProcessorProperties>



Architecture rationale WS-Resource framework exploits WS-Addressing

• Web services and WS-Resources are referenced using an “Endpoint Reference”

• Services that create or locate WS-Resources returnEndpoint References

Web service and WS-Resource are separate:• A Web service is stateless• A WS-Resource provides a context for stateful

execution• Different entities, different lifetimes, different

capabilities



WS-Notification WS-Notification

• Brings enterprise quality publish and subscribe messaging to Web services

– Loosely coupled, asynchronous messaging in a Web services context

• WS Notification exploit WS Resource framework and Web services technologies


Subscriber indicates interest in a particular “Topic” by issuing a “subscribe” request

Broker (intermediary) permits decoupling Publisher and Subscriber

“Subscriptions” are WS-Resources

• Various subscriptions are possible

Publisher need NOT be a Web Service

Notification may be “triggered” by:• WS Resource Property value changes• Other “situations”

Broker examines current subscriptions

Brokers may • “Transform” or “interpret” topics• Federate to provide scalability

Broker

Subscriber

WS-Notification

Publisher

subscribe

subscribe

S S S

notify

notify

notify

notify


WS-Notification Characteristics of WS-Notification:

• Web services integration of traditional enterprise publish/subscribe messaging patterns

– Composes with other Web services technologies– Facilitates integration between different messaging

middleware environments

• Standardizes the role of Brokers, Publishers, Subscribers and Consumers

• Provides two forms of publish/subscribe: direct publishing and brokered publishing

• Standardizes Web service message exchanges for publishing, subscribing and notification delivery

• Defines XML model of Topics and TopicSpaces to categorize and organize notification messsages


A

ServiceLevel

WS-Resource framework & WS-NotificationScenario: Grid Resource Management & Scheduling

Cluster

RRR

Mainframe

RRRIBM

IBM

Blades

RRR

Notification

GridScheduler

WS-Resource used to “model”

physical processor resources

WS-Resource Properties “project” processor status (like utilization)

Local processor manageris “front-ended” with A Web service interface

Other kinds of processors are also“modeled” as same type of

WS-Resources

JJ

J

WS-Notification can be used to “inform” the scheduler when processor utilization

changes

Grid “Jobs” and “tasks” are also modeled using

WS-Resources and Resource Properties

Grid Scheduler

is a Web Service

Service Level Agreement

is modeled as a WS-

Resource Lifetime of SLA Resource

tied to the duration of

the agreement


IBM Support for WS-Notification & WS-Resource Framework

As standards mature and are broadly adopted IBM WebSphere Family and related Rational tools

• Provide a runtime environment that supports WS-Resource Framework and WS-Notification

WS-* standards and Service Oriented Architecture (SOA) exploited:• Including WS-Security, WS-Reliable Messaging,

WS-Resource Framework, WS-Notification etc. • Fundamental to IBM’s OnDemand operating environment

– System Management, Autonomic Computing– Data Management and Storage Management– Knowledge Management and Collaboration– Business Computing Services


WS-Resource framework & WS-NotificationValue: To software developers:

• Reduced cost / time to develop software– Use of existing WS development tools– Reuse of common components– Permit interoperation with other vendors components

To customers

• Increased solution flexibility & interoperability– Support heterogeneous distributed computing environment– Create solutions from multiple vendor components– Interoperability with partners using other software– Open reference implementations available


NEXT STEPSNEXT STEPS

WS-SecurityWS-Addressing

WS-Base Faults

WS-Notification

WS-Renewable References


WS-Lifetime

WS-Service Group

Begin PublicCommentProcess

WS-Resource Framework & WS-Notification


NEXT STEPSNEXT STEPS

WS-Base Faults

WS-Notification



WS-Lifetime

WS-Service Group


InteroperabilityDemonstration



NEXT STEPSNEXT STEPSNEXT STEPSStandards

Body

WS-Base Faults


WS-Service Group





NEXT STEPSNEXT STEPSNEXT STEPSStandards

Body

WS-Base Faults


WS-Service Group




Dr. Daniel Sabbah Vice President of Strategy & Technology IBM Software Group Bringing Grid & Web Services Together Globus World San Francisco, CA Tuesday,

Documents

grid web services

ogsa services

web services outlines

web services osga

wsresource examples

web services standards

web server

web services error messages