Erl SOA Chapter 16 Part 3 (Perry)


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Erl SOA Chapter 16 Part 3 (Perry)

  1. 1. 16.3 Service Oriented business process design <ul><li>The last overall step in Service Oriented Business process design </li></ul><ul><li>Goal is to map the business processes completely </li></ul><ul><ul><li>All expected process flows are mapped </li></ul></ul><ul><ul><li>All exception conditions are anticipated and accommodated </li></ul></ul><ul><li>Traditionally work split </li></ul><ul><ul><li>business analysts modeled processes </li></ul></ul><ul><ul><li>It architects and developers built the services </li></ul></ul><ul><li>WS-BPEL makes it possible for the same person to model the process flow while creating the process service in the orchestration layer </li></ul>
  2. 2. Review existing design products <ul><li>Previous design steps created the products needed to model the business processes and create the orchestration </li></ul><ul><ul><li>Composition diagrams </li></ul></ul><ul><ul><li>Service Candidates </li></ul></ul><ul><ul><li>Service designs </li></ul></ul><ul><ul><li>Workflow logic produced modeling services </li></ul></ul>
  3. 3. Map out interaction scenarios <ul><li>Interaction between process and partner services </li></ul><ul><li>Create activity diagrams </li></ul><ul><ul><li>Diagrams of successful processes </li></ul></ul><ul><ul><li>Diagrams of unsuccessful processes </li></ul></ul><ul><li>List messages to be processed by each service </li></ul><ul><ul><li>Incoming messages </li></ul></ul><ul><ul><li>Outgoing messages </li></ul></ul>
  4. 4. Design the process service Interface <ul><li>Create WSDL process service definitions </li></ul><ul><ul><li>Typically using modeling tools </li></ul></ul><ul><ul><li>Can usually be edited by hand to ensure </li></ul></ul><ul><ul><ul><li>All Input and output values required are included </li></ul></ul></ul><ul><ul><ul><li>The portType area includes all operation constructs </li></ul></ul></ul><ul><ul><ul><li>Meta information has been included using the documentation element </li></ul></ul></ul>
  5. 5. Formalize partner service conversations <ul><li>Describe the role of each partner service in a message exchange </li></ul><ul><li>Add partnerlinkType constructs to the service WSDL definitions </li></ul><ul><li>Create partnerLink elements for each partner service in the process definition </li></ul><ul><li>Define variable elements for messages sent and received with partner services </li></ul><ul><li>This comprises the possible message flows in the process execution </li></ul>
  6. 6. Define Process Logic <ul><li>Create a WS-BPEL process definition </li></ul><ul><ul><li>Implements the original workflow logic </li></ul></ul><ul><ul><li>Encompasses processing requirements </li></ul></ul><ul><ul><ul><li>Activities </li></ul></ul></ul><ul><ul><ul><li>Fault handling </li></ul></ul></ul><ul><ul><li>Covers all the service interaction scenarios </li></ul></ul>
  7. 7. Iterative review <ul><li>Check your step 1 interaction scenarios and ensure the WS-BPEL reflects the process logic succinctly </li></ul><ul><ul><li>Ensures the original interactions scenarios are complete </li></ul></ul><ul><ul><li>Possibly leads to the discovery of new fault or exception conditions that need to be included in the WS-BPEL </li></ul></ul><ul><ul><li>Look for opportunities to consolidate activities </li></ul></ul><ul><ul><li>Clean up markup code for readability and ease of maintenance </li></ul></ul>
  8. 8. Summary <ul><li>Business Process design comes last </li></ul><ul><li>Previous design products are used in process </li></ul><ul><li>The service interface and process definition are created </li></ul><ul><li>Graphical modeling tools alleviate the need to know WS-BPEL and WS-Coordination syntax, but knowledge of the elements is essential </li></ul><ul><li>The design process is best seen as iterative with value added in streamlining, maintainability and optimization achieved through reviewing the WS-BPEL resultant document against the original workflow and previous SOA design products. </li></ul>
  9. 9. More information <ul><li>WS-BPEL 2.0 Official Primer on Oasis </li></ul><ul><ul><li> </li></ul></ul><ul><li>IBM Online - Understanding Web Services specifications, Part 7: WS-Business Process Execution Language </li></ul><ul><ul><li> </li></ul></ul><ul><li>WS-BPEL on apache – ODE (Orchestration Director Engine) </li></ul><ul><ul><li> </li></ul></ul>