10. Service Orchestration Darmstadt University of Applied Sciences, Department of Computer Science Dr. Markus Voß (Accso GmbH)

Transcription

1 SOA Service Oriented Architecture 10. Service Orchestration Darmstadt University of Applied Sciences, Department of Computer Science Dr. Markus Voß (Accso GmbH)

2 Today s topic 1. Introduction 2. Business Architecture 3. Designing Domains 4. Designing Components 5. Designing Interfaces and Operations 6. Loose Coupling 7. Excursus: Business Information Systems 8. Web Services 9. Integration 10. Service Orchestration 11. Evolution of Application Landscapes 2

3 Agenda Overview BPM BPEL 2.0 BPMN 2.0 Literature 3

4 Service orchestration in the context of the enterprise architecture framework Technical Reference Architecture Business Geschäft Information System (IS) IT Technical Infrastructure (TI) Kontextuell Contextual (warum?) (why?) Konzeptionell Conceptual (what?) (was?) Logisch Logical (how?) (wie?) Physisch Physical (with (womit?) what?) Geschäftsstrategie Business Strategy Business Architecture Business Geschäftsarchitektur Architecture (Business (Geschäftsservices, Services, Business Geschäftsprozesse, Processes, Geschäftsobjekte, Business Objects, Organisation, Organisation) etc.) IT Strategy Domänen Ideal Application Domains und Technical Landscape and Domänen Technische Services (Anwendungs-) Services Application Services und Services Domänen Technische Services (Anwendungs-) und Services Logische Technische Services Logische Logical (Anwendungs-) Logical Anwendungs- Application und and AL-Komponenten AL-Components Services Logische Logische Integration Integrationsplattformen Logische Platforms und and ihre their Schnittstellen Interfaces Anwendungs- und AL-Komponenten Logische Integrationsplattformen und ihre Schnittstellen Anwendungs- und AL-Komponenten Physische Physische Physical Integrationsplattformen und ihre Schnittstellen Physical Anwendungs- Application undand AL-Komponenten AL-Components Physische Physische Integration Integrationsplattformen Physische Platforms und and ihre their Schnittstellen Interfaces Anwendungs- und AL-Komponenten Physische Integrationsplattformen und ihre Schnittstellen Anwendungs- und AL-Komponenten Integrationsplattformen und ihre Schnittstellen Integration AS IS TO BE Evolution IDEAL 4

5 Service orchestration pattern / two level programming : Separating agile from stable parts 2nd Level Business Process More agile Modellers Domain{ { 1st Level Function and Data More stable/basic Programmers Domain 5 Quelle: M.B. Juric, M. Krizevnic: WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g

6 Service Orchestration in the context of the reference architecture <<AL>> <<AL>> <<AL>> <<AL>> xxx xxxxxxx x xxx xx xx xxxxxx xxxxxx xx xxxxx xxx xx xx cxxx xcxxxxx xxxxxx xxx xxxxxxx x xxx xx xx xxxxxx xxxxxx xx xxxxx xxx xx xx cxxx xcxxxxx xxxxxx xxx xxxxxxx x xxx xx xx xxxxxx xxxxxx xx xxxxx xxx xx xx cxxx xcxxxxx xxxxxx <<AL>> <<AL>> Service orchestration technology (BPEL 2.0 or BPMN 2.0) for implementing Business Process components <<AL>> <<AL>> <<AL>> <<AL>> <<AL>> <<AL>> Web services technologies (WSDL, SOAP, UDDI) for communication between loosely coupled components <<AL>> <<AL>> <<AL>> 6

7 Agenda Overview BPM BPEL 2.0 BPMN 2.0 Literature 7

8 BPM Business Process Management A process is a series of specified operations (activities, tasks) executed by humans or machines to achieve one or more objectives. The ultimate aim is to create customer value and thus to generate value for the company. BPM Common Body of Knowledge (EABPM*): Business Process Management (BPM) is a systemic approach geared to capture, design, execute, document, measure, monitor and control automated as well as non-automated processes in order to meet the objectives that are aligned with the business strategy of a company. BPM embraces the conscious, comprehensive and increasingly technologyenabled definition, improvement, innovation and maintenance of end-toend processes. Through this systemic and conscious management of processes companies achieve better results in a faster and more flexible way. 8 * European Association of Business Process Management

9 BPM Process Models & Layers Business-IT-Alignment Layer 1 Strategic Process Model Content: process overview Purpose: rapid understanding Business Layer 2 Operational Process Model Content: operational flow Purpose: work & implementation basis IT Layer 3a Technical Process Model Layer 3b IT Specification Content: technical details Purpose: implementation process engine usage Layer 4b Implementation without process engine 9

10 BPM Process Automation using a Process Engine Technical Process Model Modeling Monitoring and Reporting Process-Engine Human Workflow Management Turn Around Measurement (Processing Time)... Task Assignment Automated Service Invocation Automatic Decision Automated Service Invocation Task Assignment... Service- Orchestration Process Participant IT-System IT-System Process Participant 10

11 BPM Process Engine = Magic BPM Suite + Zero Code? Business User Software Developer? 11 While there are reasonable use cases for zero code BPM Suites, they are not the right approach for automating business processes that execute an IT based business model. The real problem is that most of the zero coding BPM vendors claim that you should use their solution for situations where you actually shouldn't.

12 BPM Suite Learning Curve NAIVELY CONFIDENT You think you know, but you still don t know what you don t know MASTERY ACHIEVED You know it. CLUELESS You don t know what you don t know. DISCOURAGING REALISTIC You know what you don t know. Traditional BPM Suites require a vendor specific learning curve. If your business model is IT based, your software developers are probably your most valuable assets. There are numerous Java developers specialized in Java EE concepts and integration frameworks. 12 Business-IT-Alignment is not about getting rid of IT, but a successful collaboration between partners. Allow business as well as IT to use their most productive tools - and bring them together!

13 13 BPM Notations Overview

14 EPK (Ereignisgesteuerte Prozesskette) a model for Business & IT? EPK appears simple, the symbols are more or less well known. But: EPK is neither correct nor complete. Samples: - when exactly does the timing of the 7 days start? - what is a sucessful and what an erroneous ending? - which activity is a service and which a human task? EPK is suitable for strategic process models. 14

15 BPEL 2.0 a model for Business & IT? Why BPEL is not the holy grail for BPM: BPEL = building new services by orchestrating existing services Aligned to the usage of the WS-*-Stack Restrictions due to block based design (versus graph based)! Human Task Management not before introduction of BPEL4People 15 BPEL is a technical modeling language aiming at Web Service orchestration!

16 BPMN 2.0 a model for Business & IT! BPMN 2.0 has a level of detail suitable for the operational and the technical model. 16

17 Agenda Overview BPM and BPEL 2.0 BPMN 2.0 Literature 17

18 Reference for chapter slides OASIS: WS-BPEL 2.0 (Web Services Business Process Execution Language) Technical Introduction Part 1: Frank Ryan, Active Endpoints, Inc. Part 2: Dieter König, IBM Senior Technical Staff Member Part 3: Charlton Barreto, Adobe Senior Computer Scientist/Architect 18

19 19

20 20

21 21

22 22

23 23 Overview of Language Elements

24 24

25 25

26 26

27 27

28 29

29 30

30 31

31 32

32 34

33 Example using lab technology: Simple WS Wrapper 35 <?xml version="1.0" encoding="utf-8"?> <process name="sampleprocess" targetnamespace=" xmlns=" xmlns:xsd=" xmlns:sxt=" xmlns:sxed=" xmlns:tns=" <import namespace=" location="sampleservicewsservicewrapper.wsdl" importtype=" <import namespace=" location="sampleservicewsservice.wsdl" importtype=" <import namespace=" location="sampleprocess.wsdl" importtype=" <partnerlinks> <partnerlink name="partnerlink2" xmlns:tns=" partnerlinktype="tns:sampleprocess" myrole="sampleprocessporttyperole"/> <partnerlink name="partnerlink1" xmlns:tns=" partnerlinktype="tns:sampleservicewslinktype" partnerrole="sampleservicewsrole"/> </partnerlinks> <variables> <variable name="createsampleentityout" xmlns:tns=" messagetype="tns:createsampleentityresponse"/> <variable name="createsampleentityin" xmlns:tns=" messagetype="tns:createsampleentity"/> <variable name="sampleprocessoperationout" xmlns:tns=" messagetype="tns:sampleprocessoperationresponse"/> <variable name="sampleprocessoperationin" xmlns:tns=" messagetype="tns:sampleprocessoperationrequest"/> </variables> <sequence name="sequence1"> <receive name="receive1" createinstance="yes" partnerlink="partnerlink2" operation="sampleprocessoperation" xmlns:tns=" porttype="tns:sampleprocessporttype" variable="sampleprocessoperationin"/> <assign name="assign1"> <copy> <from variable="sampleprocessoperationin" part="tourname"/> <to>$createsampleentityin.parameters/arg0</to> </copy> </assign> <invoke name="invoke1" partnerlink="partnerlink1" operation="createsampleentity" xmlns:tns=" porttype="tns:sampleservicews" inputvariable="createsampleentityin" outputvariable="createsampleentityout"/> <assign name="assign2"> <copy> <from>$createsampleentityout.parameters/return</from> <to variable="sampleprocessoperationout" part="number"/> </copy> </assign> <reply name="reply1" partnerlink="partnerlink2" operation="sampleprocessoperation" xmlns:tns=" porttype="tns:sampleprocessporttype" variable="sampleprocessoperationout"/> </sequence> </process>

34 Agenda Overview BPM BPEL 2.0 BPMN 2.0 Literature 36

35 BPMN 2.0 History and Scope History BPMN 2.0 Scope BPMN developed by IBM as of 2001, graphical notation released by BPMI in 2004 BPMN 1.0 is an official OMG standard since 2006 not executable up to and including BPMN 1.2 final version released by OMG in January, 2011 with respect to the graphical notation BPMN 2.0 differs hardly from BPMN 1.2. Only a few symbols have been added. starting with BPMN 2.0 process models are executable (i.e. technical artifacts are now well-defined and XML schemes have been provided). developed to specify processes. i.e. BPMN 2.0 does not include: process landscapes, organisational structures, data, strategies, business rules, IT landscapes. There is no need to reinvent the wheel eligible notations already exist. BPMN concentrates on processes, a process is simply a logical and chronological order of activities neither more nor less. 37

36 BPMN 2.0 Core Elements Flow Objects Connection Objects Artifacts Activity Sequence Flow Data Object Event Message Flow Group Gateway Association Note complete notation: BPMN2_0_Poster_EN.pdf Participants 38 In a process certain things need to be done (Activities), possibly only under certain conditions (Gateways), and things can happen (Events). Flow objects are connected using Sequence Flows, but only inside of a Pools or Lane. Across pool boundaries you have to use Message Flows. Artifacts deliver more information details, they are connected to flow objects using Associations.

37 BPMN 2.0 Business-IT-Alignment = Collaboration Organisational flow of process participant Process Engine 39

38 BPMN 2.0 Collaboration (Interacting Processes) Pool Blackbox Sequence Flow Process Engine Message Flow Organisational process of a participant Pool Whitebox complete showcase: onfluence/display/foxuser Guide/Twitter 40

39 BPMN 2.0 Multi-Level Escalation Sub Process Intermediate Timer Event Boundary Event Event Based Gateway Intermediate Message Event 41

40 BPMN 2.0 Error Handling Catching Error Event Throwing Error Event Terminate End Event Event Sub Process Catches a named error Catches all other errors 42

41 BPMN Compensation book hotel is multi-instance: compensation handler will be called for every successful executed instance Boundary Compensation Event Association! Compensation Handler Throwing Compensation Event 43

42 BPMN 2.0 and JEE 6 camunda platform infrastructure Source: camunda 44

43 BPMN 2.0 and JEE 6 WebService Integration Scenarios + e.g. Apache CXF 45

44 BPMN 2.0 and JEE 6 WebService Integration Scenarios Generic Implementation (JaxWsDynamicClientFactory) + e.g. Apache CXF How-To: 46

45 BPMN 2.0 and JEE 6 WebService Integration Scenarios Integration Generic Implementation (JaxWsDynamicClientFactory) ESB e.g. Mule, Apache Camel + e.g. Apache CXF How-To: 47

46 BPMN 2.0 and EAI / SOA: Typical Integration Scenario ESB complete showcase: onfluence/display/foxuser Guide/Bank+Account+Ope ning Process Engine ESB 50

47 Agenda Overview BPM BPEL 2.0 BPMN 2.0 Literature 51

48 Literature BPMN 2.0 Notation Overview BPMN 2.0 by example BPMN 2.0 Modeling Reference Praxishandbuch BPMN 2.0 Carl Hanser Verlag GmbH & Co. KG, März 2012 Open Source BPM and Workflow based on BPMN