Web service orchestration demo

BCS 27 Nov 2008

Alan Jones, Teesside branch secretary

scenario

Linking front-office with back-officeSimulated integrationCapitalising on well-known animosity

between Sales and Engineering

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 

The process

Call centre phones-in a firm orderCheck if customer already known to

Sales?YES – UPDATE Manufacturing with order.NO – update both sales and

manufacturing

Jargon

Sales systems are frequently synonymed as CRM

Manufacturing systems likewise, as ERP

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.

My modelling technique

I use Yourdon modelling to analyse ‘how many messages?’ and ‘how many ports?’

Yourdon has no semantics for its modelsWe can make the model mean whatever

we wantThe nice thing about Yourdon is it models

what’s outside the business as well as what’s inside.

Yourdon technique

What are the events?Draw a Data Flow picture for each eventAggregate all the ‘event’ pictures togetherFrom 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

events

1. Customer makes an order

Check customerInfo with

Sales

Update SalesAnd

ManufacturingERP

UpdateManuf. ERP

only

Advice NoteTo

Customer

Customerorder

SalesCRM

system

order

Yes/no no

yes

ManufacturingERP

system

Update ERP

Update CRM

Update ERPCustomer

Advice

details

details

Modelling for WSDLand BPEL

What’s a web service? WSDL

Customer – asks for an orderSales – 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

Show WSDL and BPEL simulation

http://www.activeVOS.com

Why is SOAP not SOAP any more?

SOAP was Simple Object Access ProtocolSOAP is a protocol for sending messagesBut it’s too simpleCannot answer back to a different person.Cannot encrypt message.Cannot send ‘terms & conditions’ with the

message

WS Standards

Web Service StandardsAdd extra goodies to SOAPNew addresses, encryption and codes,

terms and conditions, and lots moreAll crammed into an extended SOAPNo longer simple!