1 / 15

Web service orchestration demo

Web service orchestration demo. BCS 27 Nov 2008 Alan Jones, Teesside branch secretary. scenario. Linking front-office with back-office Simulated integration Capitalising on well-known animosity between Sales and Engineering. This demo comes from the BPEL Cook Book.

otto
Download Presentation

Web service orchestration demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web service orchestration demo BCS 27 Nov 2008 Alan Jones, Teesside branch secretary

  2. scenario • Linking front-office with back-office • Simulated integration • Capitalising on well-known animosity between Sales and Engineering

  3. This demo comes from the BPEL Cook Book About Oracle’s application of BPEL http://packtpub.com And downloadable from www.oracle.com/technology/pub/articles/bpel_cookbook/index.html

  4. The process • Call centre phones-in a firm order • Check if customer already known to Sales? • YES – UPDATE Manufacturing with order. • NO – update both sales and manufacturing

  5. Jargon • Sales systems are frequently synonymed as CRM • Manufacturing systems likewise, as ERP

  6. We’ve met this before • In this organisation, changes made in one ‘customer record’ and not updated in other systems of ‘customer record’. This problem is widespread due to ‘data silos’. • Let’s build the BPEL integration to join them. • When a customer-order is received, we check if Sales know about this customer. • If no, we tell Sales and Manufacturing. • If yes, we use information from Sales to tell Manufacturing. • Then we tell the customer what we’ve done.

  7. My modelling technique • I use Yourdon modelling to analyse ‘how many messages?’ and ‘how many ports?’ • Yourdon has no semantics for its models • We can make the model mean whatever we want • The nice thing about Yourdon is it models what’s outside the business as well as what’s inside.

  8. Yourdon technique • What are the events? • Draw a Data Flow picture for each event • Aggregate all the ‘event’ pictures together • From this big picture, you have a) the business data objects b) the messages (flows that cross the boundary) c) the ports – external entities aka services

  9. events • Customer makes an order

  10. Customer order order yes no Yes/no Sales CRM system Update CRM Update ERP Customer Manufacturing ERP system details details Update ERP Advice Modelling for WSDL and BPEL Check customer Info with Sales Update Sales And Manufacturing ERP Update Manuf. ERP only Advice Note To Customer

  11. What’s a web service? WSDL • Customer – asks for an order • Sales – has 2 tricks (aka services) • Can interrogate to find customer pre-existence • Can update with new customer data • Manufacturing has 1 service • Can update with new customer data

  12. Show WSDL and BPEL simulation • http://www.activeVOS.com

  13. Why is SOAP not SOAP any more? • SOAP was Simple Object Access Protocol • SOAP is a protocol for sending messages • But it’s too simple • Cannot answer back to a different person. • Cannot encrypt message. • Cannot send ‘terms & conditions’ with the message

  14. WS Standards • Web Service Standards • Add extra goodies to SOAP • New addresses, encryption and codes, terms and conditions, and lots more • All crammed into an extended SOAP • No longer simple!

More Related