Service Oriented Orchestration

Customer
Customer
Service
Warehouse
Shipper
Submit Order
Receive Order Validate Order
Credit Check
Inventory Check
Handle Shipment
Send Shipment
Credit
Agency
CSR Teams
Issues
a Parse XML
b Transform
c Apply Business Rules
Validate Order
a Create Outbound Msg
b Handle Response
c Apply Business Rules
Credit Check
a Send to N Warehouses
b Handle N Responses
c Determine Best WHSEs
d Handle Drop-Ships
Inventory Check
a Determine Shipper(s)
b Print Labels
c Print Pick Tickets
d Create & Send ASNs
Send Shipment
Possible Big Picture
DB
WS
Client
Application Server
Enterprise Service Bus
Action
Service D
Action
Service C
Action
Service A
JVM
Spring
DAO
EJB
Rules
Groovy
Action
Service B
O
R
C
H
E
S
T
R
A
T
I
O
N
SOAP
BPEL
Partner
Link
Partner
Link
Partner
Link
SOAP
JMS
FTP
S
E
R
V
I
C
E
Legacy
Application
SOAP
.NET
Application
SOAP
Note: Not every technology is required.
This is simply a way to illustrate how
the various technologies might be used
together
Service Orchestration & BPM
Submit Order
Receive Order Validate Order
Credit Check
Inventory Check
Handle Shipment
Send Shipment
CSR Teams
Issues
Customer CSR Sales Mgmt WHSE Mgmt Humans
J2EE App
Server

FTP
SOAP
File
Validate
Order
Credit
Check
Inventory
Check
Send
Shipment
External Credit/Bank Legacy Partners
Various Transports
An ESB Service is visible in the UDDI registry automatically. A single ESB Service may or may
not expose a WSDL. It may use out-of-the-box actions, custom actions and/or consume external
services from various sources. Focus on the reuse of existing infrastructure and assets.