WSSOA英文版培訓课件PPT第课BPEL.pptVIP

BUPTSSE SOA principles practice Lecture 8 Web Service Composition and BPEL Contents –Web Service Composition(1) Value Added Services Composition and Coordination Modeling Executable Compositions Component Model Composition Model Service Selection Model Data Transfer Model Exception Handling and Transactions Contents –Web Service Composition(2) Composition Engines Business Process Execution Language (WS-BPEL) Elements of BPEL Modeling Service Selection with Partners Message Correlation Sets Data Flow with Assignments between Variables Simple Activities Complex Structured Activities Business Processes Business Process (Example) Basic elements of BPEL Partners(1) The concept of partners is used to define the Web services that are to be invoked as part of the process. It is based on three elements: Partner Link Type: it contains two PortTypes (see WSDL), one for each of the roles in the partner entry (i.e., one portType is the portType of the process itself, the other one is the portType of the service being invoked). Partner Link: the actual link to the service. This is where the actual assignment to a binding is made (outside the scope of BPEL). Several partner links may share the same partner link type Partners: a group of Partner Links (this is an optional element). A partner link can only appear in one partner. Partners(2) The notion of Partner Link Type reflects a peer-to-peer relation between the process and each one of the services the process calls Understanding BPEL partners The notion of partner in BPEL is somewhat obscure and has changed from 1.0 to 1.1 to 2.0 In principle, the partner element is used as a vehicle for defining links: Partner Link Type: similar to a class definition in object oriented languages, it is a generic link to a given category of web service (e.g., Bookstore_purchase, Bookstore_search). The partner link type does not really specify the partner but the nature of the link and the roles played by the process and the called