Paper PresentationSYSTEMATIC THOUGHT LEADERSHIP FOR INNOVATIVE BUSINESSStrategies for Cross-OrganizationalService Composit...
SAP Research Global Network                                                         Darmstadt                             ...
Agenda  1. Executive Summary  2. Foundation and Related Work  3. Service Composition Decentralization Continuum           ...
Executive Summary   Topics              Web Service composition across company boundaries   and                       Di...
Agenda  1. Executive Summary  2. Foundation and Related Work  3. Service Composition Decentralization Continuum           ...
Automatization of Cross-Organizational  Business Transaction  Drivers and Benefits                                  Hurdle...
Orchestration vs. Choreography Orchestration                                                            Choreography   Re...
Orchestration vs. Choreography  Example                                                Choreography                Buyer  ...
Example Business Process© SAP 2007 / Page 9
Agenda  1. Executive Summary  2. Foundation and Related Work  3. Service Composition Decentralization Continuum           ...
Central Service Orchestration                       Stakeholder A                     Stakeholder B                    Sta...
Decentral Service Orchestration with Hub  Support                        Stakeholder A                    Stakeholder B   ...
Decentral Orchestration without Hub                        Stakeholder A                Stakeholder B                     ...
Evaluation Summary© SAP 2007 / Page 14
Agenda  1. Executive Summary  2. Foundation and Related Work  3. Service Composition Decentralization Continuum           ...
Declarative Service Organization  Architecture Style: Event-Driven Architecture (EDAs)     Conceptual extension of the pr...
Case Study: Event-Bus Switzerland (EBS)                              Event-Bus Switzerland (EBS)                          ...
Agenda  1. Executive Summary  2. Foundation and Related Work  3. Service Composition Decentralization Continuum           ...
Conclusion and Outlook  3   different stategies for service composition across company      boundaries where analyzed.  ...
Thank you!  Christoph.Schroth@sap.com, Till.Janner@sap.com, Volker.Hoyer@sap.com© SAP 2007 / Page 20
Upcoming SlideShare
Loading in...5
×

Strategies for cross organizational service composition

228

Published on

The automation of cross-organizational business processes bears great potential for companies to extend their market reach, save time, cut costs and respond to customer queries more agilely. However, technological support for the efficient organization of providing and consuming services across corporate boundaries is still not mature enough to allow for a large-scale adoption particularly among small-and medium-sized enterprises. In this article, we propose and evaluate different strategies with regard to architectures supporting the organization of service interconnections: In case of rather standardized and stable business relationships and interactions, a central service orchestration architecture, a hybrid orchestration approach with hub support and finally a fully decentralized peer-to-peer solution without any central control entity are proposed and compared in detail. In cases where business processes are highly complex, variable and dependent on situational factors, we propose a more implicit, declarative service orchestration methodology which builds upon Event-Driven Architectures (EDAs). For the different architectural strategies, we provide real-world exemplary implementations to prove their applicability and to investigate their strengths and weaknesses.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
228
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Strategies for cross organizational service composition

  1. 1. Paper PresentationSYSTEMATIC THOUGHT LEADERSHIP FOR INNOVATIVE BUSINESSStrategies for Cross-OrganizationalService Composition Christoph Schroth1 2, Till Janner1 2, Volker Hoyer1 2 {christoph.schroth, till.janner, volker.hoyer} @ {sap.com | unisg.ch} 1 University of St. Gallen, Institute for Media and Communications Management 2 SAP Research CEC St. Gallen, Switzerland
  2. 2. SAP Research Global Network Darmstadt Dresden Belfast Montréal Karlsruhe Walldorf St.Gallen Shanghai Palo Alto Sophia Antipolis Zurich Pretoria Brisbane SAP Labs-based Research Centers Campus-based Engineering Centers planned© SAP 2007 / Page 2
  3. 3. Agenda 1. Executive Summary 2. Foundation and Related Work 3. Service Composition Decentralization Continuum 3.1. Central Orchestration 3.2. Decentral orchestration, hub supported 3.3. Decentral orchestration without hub 3.4. Evaluation Summary 4. Declarative Service Composition (Case Study Event-Bus Switzerland) 5. Conclusion and Outlook© SAP 2007 / Page 3
  4. 4. Executive Summary Topics  Web Service composition across company boundaries and  Different strategies/ architecture possible Challenge Method  Analysis of central, hybrid with hub support, and fully decentralized service and orchestration architectures Approach  Evaluation and comparison on the basis of 8 criteria  Service Composition decentralization continuum  Hybrid approach is most promising as it unifies the adavantages of both Results centralized and decentralized solutions  Declarative Service Composition is needed in cases where processes are not well standardarized or stable© SAP 2007 / Page 4
  5. 5. Agenda 1. Executive Summary 2. Foundation and Related Work 3. Service Composition Decentralization Continuum 3.1. Central Orchestration 3.2. Decentral orchestration, hub supported 3.3. Decentral orchestration without hub 3.4. Evaluation Summary 4. Declarative Service Composition (Case Study Event-Bus Switzerland) 5. Conclusion and Outlook© SAP 2007 / Page 5
  6. 6. Automatization of Cross-Organizational Business Transaction Drivers and Benefits Hurdles of Adoption  Improvements of cost-  Different standards and performance ratio of IT standardization approaches  Extending market reach prevent from a common  Saving time  Cutting costs ! understanding of business processes and data  Responding to customer  High costs and complexity of demands more agilely existing approaches SOA aims at closing this gap© SAP 2007 / Page 6
  7. 7. Orchestration vs. Choreography Orchestration Choreography  Represents the relation between  Bird‘s eye view one central service and different  Message exchange described from other ones called according to a the perspective of an observer who pre-defined sequence is able to see all interaction of the  Adequate to describe exchange patterns of one individual service vs. participants of a choreography  Languages, e.g. WS-CDL, BPSS  Can be conducted with the help of  Not executable, used for modelling languages such as BPEL and monitoring  Executable on respective engines Modelling the overall choreography and derive executable orchestrations© SAP 2007 / Page 7
  8. 8. Orchestration vs. Choreography Example Choreography Buyer Seller PO Request Transform Send PO Receive PO Transform From From ERP ERP Retrieve PO PO Request Ack Send PO Ack Ack To ERP PO Response To ERP Rec PO Send PO Transform Transform Response Response Orchestration© SAP 2007 / Page 8
  9. 9. Example Business Process© SAP 2007 / Page 9
  10. 10. Agenda 1. Executive Summary 2. Foundation and Related Work 3. Service Composition Decentralization Continuum 3.1. Central Orchestration 3.2. Decentral orchestration, hub supported 3.3. Decentral orchestration without hub 3.4. Evaluation Summary 4. Declarative Service Composition (Case Study Event-Bus Switzerland) 5. Conclusion and Outlook© SAP 2007 / Page 10
  11. 11. Central Service Orchestration Stakeholder A Stakeholder B Stakeholder C Application Application Application Adapter Adapter Adapter Service Interface BPEL Collaborative Data & Process User BPEL Generator Modeling Templates Registry Engine Server Pro Con  Efficient monitoring  Invocation policies (not all services might be called by one  Fault handling single hub)  Maintenance  Lack of trust  Less local complexity  Single point of failure© SAP 2007 / Page 11
  12. 12. Decentral Service Orchestration with Hub Support Stakeholder A Stakeholder B Stakeholder C Application Application Application Adapter Service Adapter Adapter Interface BPEL BPEL BPEL Engine Engine Engine Derived BPEL Peer Process BPEL Collaborative Data & Process User Generator Modeling Templates Registry Server Pro Con  Message exchange independent  Fault handling more complex from server  Users must be able to handle an  Overall choreography can still be execution engine used for monitoring and fault handling support  Increased complexity© SAP 2007 / Page 12
  13. 13. Decentral Orchestration without Hub Stakeholder A Stakeholder B Stakeholder C Application Application Application Adapter Service Adapter Adapter Interface BPEL BPEL BPEL Engine Engine Engine Derived BPEL Peer Process BPEL Generator BPEL Generator BPEL Generator Modeling Modeling Modeling Templates Templates Templates Sync Sync User Registry User Registry User Registry Con Pro  Permanent synchronization of  Robustness against partial errors the local repositories  Higher scalability  Complicated fault handling  Highest complexity on client side© SAP 2007 / Page 13
  14. 14. Evaluation Summary© SAP 2007 / Page 14
  15. 15. Agenda 1. Executive Summary 2. Foundation and Related Work 3. Service Composition Decentralization Continuum 3.1. Central Orchestration 3.2. Decentral orchestration, hub supported 3.3. Decentral orchestration without hub 3.4. Evaluation Summary 4. Declarative Service Composition (Case Study Event-Bus Switzerland) 5. Conclusion and Outlook© SAP 2007 / Page 15
  16. 16. Declarative Service Organization Architecture Style: Event-Driven Architecture (EDAs)  Conceptual extension of the principles of SOA  Communication patterns (one-way notification, request/ response, notification, confirmation, etc.)  Central communication layer (Event-Bus) Three major components  Event-Bus  Middleware module  Takes over institutional funcationality (message formats, routing information formats, security, reliability)  Adapters  Ensure connectivity and interoperability  Coordination Services  Finite state-machines (FSMs) are used to describe the behavior of even-driven services© SAP 2007 / Page 16
  17. 17. Case Study: Event-Bus Switzerland (EBS) Event-Bus Switzerland (EBS) S S S EBS Services S Virtual EBS External ES Directory Services Stakeholder Sub-Bus SP Event/ Catalogue services Transformation Services S S S S SecurityServices State ES Sub-Bus Operating Services SP Tracing Services S S S S Abo Services Canton ES Error Services Sub-Bus Exception Services SP Validation Services S S S S Routing Services Munici- pality ES Sub-Bus Special Services SP© SAP 2007 / Page 17
  18. 18. Agenda 1. Executive Summary 2. Foundation and Related Work 3. Service Composition Decentralization Continuum 3.1. Central Orchestration 3.2. Decentral orchestration, hub supported 3.3. Decentral orchestration without hub 3.4. Evaluation Summary 4. Declarative Service Composition (Case Study Event-Bus Switzerland) 5. Conclusion and Outlook© SAP 2007 / Page 18
  19. 19. Conclusion and Outlook 3 different stategies for service composition across company boundaries where analyzed.  Comparison and evaluation on the basis of 8 criteria  The hybrid approach is the most promising strategy within the service composition decentralization continuum  Declarative Service Composition is needed in cases where processes are not well standardized or stable  Prototypical realization in different research projects ongoing (EU funded project GENESIS, Swiss national funded project HERA).© SAP 2007 / Page 19
  20. 20. Thank you! Christoph.Schroth@sap.com, Till.Janner@sap.com, Volker.Hoyer@sap.com© SAP 2007 / Page 20
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×