Web Service Middleware – An Infrastructure For Near Future Real Life

Web Service Ecosystems

Jan Schulz-Hofen SAP Research Center Palo Alto SAP Labs, LLC, Palo Alto, CA 94304,USA

Hasso-Plattner-Institute for Software System Engineering University of Potsdam, Potsdam, Germany

IEEE International Conference on Service-Oriented Computing and Applications (SOCA’07)

報告學生： 69621509 鄭巧玟　　指導教授：吳秀陽

Outline Introduction Preliminaries Developing a Web Service Middleware Considerations for operation of a Web Service

Middleware Conclusion

Introduction Build the Web Service ecosystem

Service broker Charging and payment facility Authenticated and fulfillment

Proposes a supporting infrastructure

Preliminaries Service-oriented Architecture Web service Ecosystem Scenario

SOA structure

Generic organizational structure in an SOA

Web Service Ecosystem

Service supply and distribution supported in the web service ecosystem framework

Alistair Barros, Marlon Dumas, and Peter Bruza. “ The Move to Web Service Ecosystem. “ BPTrends, November 2005

Scenario

Web Service Ecosystem scenario at design and time

Developing a Web service middleware Registry Charging and Penalization Monitoring and Fulfillment QoS Statistics Authentication

Registry architecture

Registry properties Service Instance

Price QoS Guarantee A reference to a service type

Service Type Functional properties described in human-readable

text and keywords A set of call parameters and their data types

Service Queries and WSDL Identity

Service instances data structure

Service type data structure

Charging and penalization Between service requestors and providers are

the lack of natural and mutual trust Organizational borders or at least bound to

predefined long-term business agreements Like unfulfilled service guarantees or

unjustified invoices can quickly emerge to major problems and to renunciation of participants from ecosystem

Two main facilities of the service broker Charging penalization

Monitoring and Fulfillment Between requestor and provider and inserts a

monitoring interceptor Log each service request and response Forward all messages to the respective receiver

transparently Intercepting machines and trust issues

The interceptor has a direct connection to the fulfillment analyzer Read access to the specified Qos properties of each

service Evaluate whether or not guarantees have been

adhered to as well as how much each service invocation has costced

Charging and penalization structure

QoS Statistics Statistics prove stability for a certain QoS level

Offering only those weak QoS properties would most probably be traded at a lower price

Allowing for small competitors to enter the market and to introduce strong QoS guarantees at a later point in time

QoS broker architecture

Tao Yu Kwei-Jay Lin. “ A Broker-based Framework for QoS-aware Web Service Composition. “ eee, 00:22-29, 2005

Authentication facility

Considerations for operation of a web service middleware Operator Procurement

Operator A high level of trust must be committed by

service requestors and providers The operator has to ensure the faultless

operation of all facilities

Procurement of middleware facilities

Procurement Authentication

Google accounts Microsoft passport

Payment Paypal Moneybookers

Monitoring VeriSign Thawte

Statistics

Conclusion Web service ecosystem an approach to realize

a supporting and market-building infrastructure which Web service middleware Assessment

Exhaustive service description Uniqueness of service type descriptions Trustworthy operation of message interceptors

Outlook Service adaptation and mediation Business transactions Transaction management More sophisticated semantics in service description

END

謝謝大家 !!