Transcript WSDL and BPEL - British Computer Society

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
About Oracle’s application of BPEL
http://packtpub.com
And downloadable
from
www.oracle.com/technology/
pub/articles/bpel_cookbook/i
ndex.html
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
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 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.
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
events
1. Customer makes an order
Modelling for WSDL
and BPEL
Customer
order
Check customer
Info with
Sales
no
Sales
CRM
system
Update Sales
And
Update CRM Manufacturing
ERP
Manufacturing
ERP
system
yes
Update
Manuf. ERP
only
Customer
Advice Note
To
Customer
Advice
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
Show WSDL and BPEL simulation
http://www.activeVOS.com
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
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!