1. 6th Expert Meeting Business Process Management (BPM) Business Activity Monitoring (BAM) Complex Event Processing (CEP) Service Oriented Architecture (SOA) Event Driven Architecture (EDA) SOA appropriate remodeling of the business process (Haspa Process)

2. 14.01.2008 6th Expert Meeting Structure  Orchestration & Choreography  WSDL  Hands-on WSDL  Compensation and Exception  Hands-on Compensation and Exception  People links  Conclusion

3. 14.01.2008 6th Expert Meeting Orchestration & Choreography ChoreographyOrchestration BPDM supports two fundamental views on processes, which complements each others Orchestration & Choreography – WSDL – Exception – Compensation – People Links

4. 14.01.2008 6th Expert Meeting Orchestration  is a short runner:  the processes are in one organization (= a unit with an established process flow)  central control  is one sequence  finish in a part of a second Orchestration & Choreography – WSDL – Exception – Compensation – People Links

5. 14.01.2008 6th Expert Meeting Choreography  is a long runner  describe the interactions between two or more organizations  no central control  helps to keep the enterprise loosely coupled and agile Orchestration & Choreography – WSDL – Exception – Compensation – People Links

6. 14.01.2008 6th Expert Meeting An easy mental link …  there’s someone — the conductor — who tells everybody in the orchestra what to do and makes sure they all play in sync.  every dancer follows a pre-defined plan — everyone is independently of the others. Choreography: Orchestration: Orchestration & Choreography – WSDL – Exception – Compensation – People Links

7. 14.01.2008 6th Expert Meeting WSDL WSDL Orchestration & Choreography – WSDL – Exception – Compensation – People Links

8. 14.01.2008 6th Expert Meeting WSDL is platform- and language-independent and describes four critical pieces of data: Interface information describing all publicly available functions Data type information for all message requests and message responses Binding information about the transport protocol to be used Address information for locating the specified service WSDL Orchestration & Choreography – WSDL – Exception – Compensation – People Links

9. 14.01.2008 6th Expert Meeting Services are defined using six major elements: : What data types will be transmitted? : What messages will be transmitted? : What operations (functions) will be supported? : How will the messages be transmitted on the wire? What SOAP- specific details are there? : Where is the service located? : What address is specified for a binding? WSDL Orchestration & Choreography – WSDL – Exception – Compensation – People Links

10. 14.01.2008 6th Expert Meeting Client Server Client Server Client Server Client Server  One-way  Request- Response  Solicit- Response  Notification WSDL – portType Message exchange patterns: WSDL Orchestration & Choreography – WSDL – Exception – Compensation – People Links

11. 14.01.2008 6th Expert Meeting Messages Types PortTypesOperations BindingsOperations ServicesPorts include refer to abstract definitions concrete definitions modifiy Elements of WSDL: WSDL Orchestration & Choreography – WSDL – Exception – Compensation – People Links

12. 14.01.2008 6th Expert Meeting

13. 14.01.2008 6th Expert Meeting SOA Exception Management SOA Exception Management challenges There is a need for an exception management solution when we move from a component oriented world to a service oriented world. Exception Management domain broadly covers  exception logging  exception notification and  exception handling Orchestration & Choreography – WSDL – Exception – Compensation – People Links

14. 14.01.2008 6th Expert Meeting SOA Fault handling and compensation At some stage in a business process an issue may arise.  some process is not completing due to an internal error  business condition has not been met  business process indicates that a failure scenario has been reached But the BPEL process may have already invoked several other Web services Fault handling and compensation Orchestration & Choreography – WSDL – Exception – Compensation – People Links

15. 14.01.2008 6th Expert Meeting Compensation is the process of undoing successful work.  Defines how a system is to attempt to recover itself when parts (or all) of a BPEL process fails. Orchestration & Choreography – WSDL – Exception – Compensation – People Links SOA Fault handling and compensation

16. 14.01.2008 6th Expert Meeting  An approach for maintaining consistency over multiple systems. Process A B C B C Atkivität COMP-C.1 Aktivität A.1ERROR Orchestration & Choreography – WSDL – Exception – Compensation – People Links SOA Fault handling and compensation

17. 14.01.2008 6th Expert Meeting Problem:  a business process may book a flight and a hotel. If the flight reservation is successful, but the hotel reservation is not, the flight must be cancelled to restore the original state. Compensation is user-defined and depends on the concrete problem at hand Solution:  the compensation handler could contact the airline Web service again and cancel the flight or inform the person if another flight date would also be possible Orchestration & Choreography – WSDL – Exception – Compensation – People Links SOA Fault handling and compensation

18. 14.01.2008 6th Expert Meeting Compensation handler  contains arbitrary activities for a scope which undoes the regular work of the scope Compensate activity  performed in the event that not all corresponding updates of different systems succeed <invoke operation="CancelFlight"... <invoke operation=“Confirm"...... <compensate scope=“BookCar" /> Orchestration & Choreography – WSDL – Exception – Compensation – People Links SOA Fault handling and compensation

19. 14.01.2008 6th Expert Meeting Conclusion  Compensation leads to looser coupling (concept of reducing the dependencies between systems) of systems  Could require more effort to implement  BPEL has direct support for compensation Since all services should be reusable, compensation is also important if no compensation is needed for the original project Orchestration & Choreography – WSDL – Exception – Compensation – People Links SOA Fault handling and compensation

20. 14.01.2008 6th Expert Meeting

21. 14.01.2008 6th Expert Meeting Human Tasks  The actual Business Process Execution Language - BPEL 2.0 - has no standard for human tasks.  Of course all BPLE vendors integrate human tasks, but they all do it slightly different.  In 2005 SAP and IBM proposed “BPEL4People“, an optional extension to BPEL 2.0 which standardized human tasks in BPEL processes and published a white paper on that subject. SOA – Human Tasks Orchestration & Choreography – WSDL – Exception – Compensation – People Links

22. 14.01.2008 6th Expert Meeting Orchestration & Choreography – WSDL – Exception – Compensation – People Links BPEL4People Source: “ WS-BPEL Extension for People – BPEL4People“ by IBM and SAP SOA – Human Tasks

23. 14.01.2008 6th Expert Meeting People links  There are only a few business processes without human interaction.  With the existing tools it is possible to create a association between the task and the person or group of persons who (can) execute the task. Orchestration & Choreography – WSDL – Exception – Compensation – People Links but this can not be translated into BPEL.  SAP and IBM create in their white paper something called „people link“:  „People links are used to represent the different groups of people who participate in the execution of a process. The group of people associated with a generic human role is determined by a people link“. SOA – Human Tasks

24. 14.01.2008 6th Expert Meeting Résumé  In 2007 – shortly before BPLE 2.0 was announced – the white paper of BPEL4People was rejected.  Maybe standardizing the portType and basic features of the task management service would be a more practical approach than BPEL4People Bruce Silver Orchestration & Choreography – WSDL – Exception – Compensation – People Links SOA – Human Tasks

25. 14.01.2008 6th Expert Meeting

26. 14.01.2008 6th Expert Meeting  Importing BPEL from a BPA-Tool in a BPM-Platform is leading to problems  Orchestration, choreography servers, implementation of WSDL and human interaction to complicated for the operating department  IT-department is overwhelmed  Expert knowledge is necessary  Danger of a bottleneck our opinion: would be better to separate the cooperate modeling into an extra tool Conclusion

27. 14.01.2008 6th Expert Meeting Thank you for your attention! Presentation: KK atja Borschert KK atharina Faustmann MM atthias Gerl MM atthias Multerer MM ichael Preu FF lorian Priller MM anuela Weiß In the background: AA rmin Eigenstetter RR enate Schambeck MM artin Schober SS andra Stein TT anja Stork TT huy-Van Truong