1. SE 548 Process Modelling WEB SERVICE ORCHESTRATION AND COMPOSITION ÖZLEM BİLGİÇ

2. Overview Definition of Web Services General View of Orchestration and Choreography Orchestration vs. Choreography Early Work in Web Service Orchestration Literature BPEL4WS Web Service Composition Example with BPEL4WS

3. Web Services Web Services can convert your application into a Web-application, which can publish its function or message to the rest of the world.

4. Web Services Communicate using open protocols Self-contained and self-describing Can be discovered using UDDI Can be used by other applications XML is the basis for Web services

5. Web Services The basic Web services platform is XML + HTTP. XML provides a language which can be used between different platforms and programming languages and still express complex messages and functions. The HTTP protocol is the most used Internet protocol.

6. Web Services Platform Elements Web services platform elements: SOAP (Simple Object Access Protocol) UDDI (Universal Description, Discovery and Integration) WSDL (Web Services Description Language)

7. WS-Platform SOAP : SOAP is an XML-based protocol to let applications exchange information over HTTP. It is platform and language independent.

8. WS-Platform WSDL : It is an XML-based language for locating and describing Web services WSDL document structure composed by types : The data types used by the web service messages : The messages used by the web service portType : The operations performed by the web service The communication protocols used by the web service

9. The Main Structure of WSDL Document

10. WS-Platform UDDI : UDDI is a directory service where companies can register and search for Web services. It stands for Universal Description, Discovery and Integration It uses WDSL to describe interfaces to web services UDDI communicates via SOAP

11. Orchestration It describes describes how web services can interact with each other at the message level, including the business logic and execution order. With orchestration, the process is always controlled from the perspective of one of the bussiness parties.

12. Composition Of Web Services with Orchestration

13. Choreography It relates to describing externally observable interactions between web services It is based on collaboration It tracks the sequence of public message exchanges that occur between multiple sources, including customers, suppliers, partners

14. Composition Of Web Services with Choreography

15. Orchestration vs. Choreography Orchestration Centralized through explicit definitions of operations and the invocation order of Web Services A single director in control Choreography Tracks the sequence of publicly visible message exchange between multiple services Participants has to know exactly when to become active

16. Early Work Many languages have emerged in the literature for web service orchestration including WSCL, XLANG AND WSFL.

17. Web Service Conversation Language(WSCL) A simple conversation language standart based on modeling the sequnces of interactions among web services. It enables to define the abstract interfaces of web services.

18. WSCL Example

19. XLANG It was developed by Microsoft. Focused on the creation of business processes and the interactions between web service providers. The specification provided support for sequential, parallel, and conditional process control flow. XLANG used WSDL as a means to describe the service interface of a process.

20. Web Service Flow Language(WSFL) WSFL was developed by IBM to specify public as well as private processes. It defines the execution order of activities and data exchanges for a process. It was integrated with XLANG language to create a BPEL4WS.

21. Orchestration Products OpenStorm Service Orchestrator Microsoft BizTalk Server Collaxa IBM WebSphere Process Choreographer BEA WebLogic 8.1 …

22. Bussiness Process Execution Languages for Web Services (BPEL4WS) BPEL4WS (Business Process Execution Language for Web Services) has recently been developed as a new workflow specification by IBM, Microsoft, and BEA BPEL4WS is a specification that models the behavior of web services in a business process interaction This specification is a result of integrating both XLANG and WSFL

23. BPEL4WS The specification provides an XML-based grammar for describing the control logic required to coordinate web services participating in a process flow. This grammar can then be interpreted and executed by an orchestration engine, which is controlled by one of the participating parties.

24. BPEL4WS Process Flow A BPEL4WS process defines the order in which involved Web services are composed, either in sequence or in parallel.

25. BPEL4WS BPEL4WS provides support for both executable and abstract business processes. An executable process models the behavior of participants in a specific business interaction, essentially modeling a private workflow. Abstract processes, modeled as business protocols in BPEL4WS, specify the public message exchanges between parties.

26. How to bulid a BPEL process? A process consists of a set of activities. It interacts with external partner services through a WSDL interface. To define a BPEL process, we use 1. A BPEL source file (.bpel) which describes the execution order, activities and conditional behaviours. 2. A process interface (.wsdl) that defines the ports, the namespace, partner link types, operations, and messages which are required to determine process activities. WSDL files are needed in order to create a valid, executable BPEL definition.

27. BPEL4WS Process Elements and Properties A BPEL process contains several structural parts:

28. BPEL4WS Process Elements and Properties The process element : It is the root element of BPEL process definition. It has a name attribute and it is used to specify the definition related namespaces. Partner Links elements : These elements in a BPEL process define the interaction of participating services with the process. Variables elements : A BPEL process allows to declare variables in order to receive, manipulate, and send data. Fault Handlers element : A fault handler determines the activity which the process has to perform when an error occurs. Correlation Sets element : Message correlation is the BPEL mechanism which enables several processes to interact in Stateful conversation. Event handling element : An event handler allows the scope to response to events, or the expiration of timers, at any time during the execution of a scope.

29. BPEL4WS Process Elements and Properties Activities elements : Activities are the processing steps, performed in a BPEL body. Primitive Activities : invoking other Web services’ operations. : waiting for the client to invoke the business process by sending a message. : generating a response for synchronous operations. : manipulating data variables. : indicating faults and exceptions. : waiting for some time. : terminating the entire process.

30. BPEL4WS Process Elements and Properties Structure and control activities : The combination of the primitive activities described above enables to build complex algorithms which define exactly the steps of business processes. : defining a set of activities that will be executed in an ordered sequence. : defining a group of activities which will be invoked in parallel. : Case-switch construct for implementing branche : defining loops. : selecting one of several alternative paths.

31. Web Service Composition Example with BPEL4WS In this example, we show a client making a request in order to buy a flight ticket, rent a car and reserve a room for his travel. The Travel Agent (central process) will communicate with a hotel service, a car rent service and an airline service to fulfill the client’s wishes. Once a reservation is made, it is sent back to the client.

32. Travel Reservation Agent Process

33. A simplified bussiness process for a travel reservation agent is defined: The client invokes the business process, specifying his name, the destination, the departure date and the return date. The BPEL process checks if it is possible to book the flight ticket with Airline A. We assume that Airline Company A provides a Web service through which such bookings can be made. Then the BPEL checks if it is possible to rent a car from Car-Rent Company. We assume as well that the Car-Rent Company provides a web services through which such renting can be made. Finally, the BPEL process reserves a room from a hotel and returns the travel reservation summary to the client. We build a synchronous BPEL process. We assume that the Web services for booking the air plane ticket and the hotel as well as renting the car are synchronous because such data can be obtained immediately and returned to the requestor.

34. Getting Familiar With the Involved Web Services Before starting the BPEL process definition, we need to get some information about the Web services involved in the process. These services are called partners. This example involves the Airlines web service, the Hotel web service and the Car rent web service.

35. Airline Web Service The A Airline Web service is synchronous. It specifies one port type: AirlineReservation which is used to book flight tickets through the bookTicket operation. This operation returns the reservation result to the process

36. Hotel Web Service The Hotel web service provides the HotelReservation portType through which the room can be reserved by calling the reserveRoom operation. This operation will have an input message called reserveRoom and an output message (return message) reserveRoomResponse which contains a confirmation and the room number

37. Car Web Service The Car Web service provides the CarReservation portType through which the car can be rent by the client by calling the rentCar operation. This returns a confirmation and the car type attributed to the client

38. Define WSDL for the BPEL Process The WSDL specification of the process defines the available port types for its clients as well as operations, messages, partner link types, and properties of interest to the process. The process receives messages from its clients and returns results.

39. WSDL for the Process

40. Define Partner Link Types In this example, there are four different partners: the client who requests the reservation and invokes the Process, the airline web service to book the flight ticket, the hotel web service to book a room and the car rent web service. The WSDL of the process imports the WSDL of other web services providers and defines the partner link types for them. ClientPartnerLink : Used to describe the interaction between the client and the BPEL process itself. AirlinePartnerLink : used to describe the interaction between the Airline service provider and the BPEL process itself. HotelPartnerLink : used to describe the interaction between the BPEL process and the Hotel Reservation Web service. CarPartnerLink : describes the interaction between the BPEL process and the Car Rent Web service.

41. Define the Bussiness Process The BPEL process waits for an incoming message from the client which starts the execution of the business process. In our example, the client initiates the BPEL process through sending an input message.

42. Define the Bussiness Process The main elements of the BPEL process construction: Namespaces: here we define the target namespace and the namespaces to access the Airline WSDL, Hotel WSDL, Car WSDL, and the BPEL process WSDL description files. Variables: they are used to store, reformat and transform messages. Each variable has a specific type like a WSDL message type, an XML Schema Simple Type. Process logic definition: the process main body specifies the order in which the partner Web services are invoked. In our example, we start with a that allows defining several activities that will be performed sequentially.

43. The Simplified BPEL Process

46. Client Implemantation

47. Client Request Result

48. THANK YOU