Professional Documents
Culture Documents
BPM, Web Services, and Standardization
BPM, Web Services, and Standardization
Michael zur Muehlen Center of Excellence in Business Process Innovation Howe School of Technology Management Stevens Institute of Technology mzurmuehlen@stevens.edu
Process Design
Process Models
Animation, Simulation
Metrics, Targets
Process Evaluation
Target Values
Process Implementation
Process Metrics
Process Enactment
Measure -ments
Process Metrics
Process Monitoring
Implemented Processes
Proliferation of Standards What do they mean BPM standards have not been successful? On the contrary, they have been so successful that everybody has their own!
- Mark Twain
(if he were alive today)
Workflow Standardization
1994 1 standardization group for workflow Reference model + 5 interface standards Size of the average specification ~40 pages 2004 10+ standardization groups with interest in workflow 7+ standards for process models alone Size of the average specification ~100 pages Wasnt XML supposed to make our life easier?
2004 M. zur Muehlen - All Rights Reserved.
2004
BPM Layer Still many choices Presentation Format HTML Message Format SOAP Data Format XML Packet Layer TCP, HTTP Network Ethernet
standardized
Web Services
Access remote service Protocol Based: Technology Independent .net Java XML Based: X-platform, X-OS WSDL definition of the interface UDDI to look for service Web Services is a sure bet
Choreography
Single Invocation of Web Service is well defined. Multiple Invocation, or Invocation of Multiple Web Services What constraints exist on order? What side effects will there be? How do I back out in the middle? How to get idempotent (all-or-none) behavior?
Process Integration
Organization A
Private Processes Private Process A1 Public Processes Public Process
Organization B
Public Processes Public Process Private Processes Private Process
A2
A3
C1
message
D1
E1
A4
B2
B3
C3
message
D3
E4
Legend An Activity(n) Control Flow Data Flow Service Flow Operations: Semantics Addressing Exception Handling Messages: Content Encoding Sequencing Routing Ports: Addressing Access Authentication
Process Integration Standards Areas Reserved. 2004 M. zur Muehlen - All Rights
source: www.rosettanet.org
2004 M. zur Muehlen - All Rights Reserved.
Quote
Long running business interactions are composed of multiple request-response conversations The state of the overall interaction must be kept by either party, to detect messages that are out of sync or uncorrelated This is the domain of web services choreography standards
Delivery Note
2003
BPM Layer Still many choices Presentation Format HTML Message Format SOAP Data Format XML Packet Layer TCP, HTTP Network Ethernet
standardized
WSCL W3C
WSDL W3C
BEA CSC Chevron Cisco CommerceOne DHL E2Open FedEx Fujitsu HP IBM Intalio Intel iWay Izar, Inc. Lucent Microsoft Netscape Netfish Oracle SAP SeeBeyond Siebel Staffware SUN Telcordia UPS Versata
Process Interoperability
A matter of taste
The workflow system does not do the work! It only coordinates the work of others. And..
Initiate Purchase
The workflow system did not initiate the process, it is merely performing in response
Initiate Purchase
Workflow System
Interoperability
Interoperability Standards
Workflow 1
Interoperability Standards
Workflow 2
Operation-Oriented Workflow
SOAP Server Create Purchase Order SOAP Client Invocator Connector SOAP Message Get Purchase Order Status A1 Process Interface Process Model
A2
A3
A4
Observer PurchaseOrde rStateChange dListener PurchaseOrder Updated Listener PurchaseOrder Completed Listener SOAP Message
A1
A2
A3
Connector
A4
Resource-oriented Workflow
REST Client REST Server Process Factory Invocator GET URI Process InfoXML Connector POST (Context) URI Process Instance URI A4 A2 A3 Process Model A1
Observer
URI A2
A3 URI
URI A4
BPEL is operation-oriented
Powerful Design Tools Needed Inflexible, change only by going back to design Many standards need to be in place
Wf-XML is resource-oriented
Easy to link at any time No upgrade problems But links can break, must handle at run time