1. 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 鄭巧玟 指導教授：吳秀陽

2. Outline  Introduction  Preliminaries  Developing a Web Service Middleware  Considerations for operation of a Web Service Middleware  Conclusion

3. Introduction  Build the Web Service ecosystem  Service broker  Charging and payment facility  Authenticated and fulfillment  Proposes a supporting infrastructure

4. Preliminaries  Service-oriented Architecture  Web service Ecosystem  Scenario

5. SOA structure Generic organizational structure in an SOA

6. 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

7. Scenario Web Service Ecosystem scenario at design and time

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

9. Registry architecture

10. 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

11. Service instances data structure

12. Service type data structure

13. 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

14. 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

15. Charging and penalization structure

16. 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

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

18. Authentication facility

19. Considerations for operation of a web service middleware  Operator  Procurement

20. 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

21. Procurement of middleware facilities

22. Procurement  Authentication  Google accounts  Microsoft passport  Payment  Paypal  Moneybookers  Monitoring  VeriSign  Thawte  Statistics

23. 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

24. END  謝謝大家 !!