Escolar Documentos
Profissional Documentos
Cultura Documentos
Robert M. Shapiro Chair, Process Interchange, WfMC Senior Vice President, Research Global 360
11:30-12:30
12:30-1:00
1:45-2:15 2:15-2:30
2:30-3:00 3:00-3:30 3:30-4:30
Analytics BPAF
BPEL Modeling Open Discussion
BPEL Proposed Standard Web Service composition language Used for web service orchestration BPEL was originally developed by BEA, IBM, and Microsoft. Version 1.1 also includes input from SAP and Siebel. The OASIS TC Web Services Business Process Execution Language now continues the standardization of BPEL BPEL 2.0 Officially adopted in June 2007
* Extracted
from Goals of the BPEL4WS Specification by Leymann, Roller, and Thatte, working document submitted to OASIS August 25, 2003
* Extracted
from Goals of the BPEL4WS Specification by Leymann, Roller, and Thatte, working document submitted to OASIS August 25, 2003
Coordination
SOAP (Logical Messaging) XML, Encoding Other protocols Other services
Ownership/Issue Information
Vendor B Process Modeling
Resources/Time Information
Vendor C Process Simulation
Goals/Strategies
Vendor D Process Optimization
Limited Portability
People Integration
It is generally not possible to design a process with a tool from one vendor and execute it in another vendors engine
But exchange between design tools is possible
BPEL vs. XPDL (whats common) Process definition standards XML based Built on process flows based on activities Support inter-process messaging based on WSDL Supported by customers, vendors, consultants, academics and governments Adopted by major BPM/ECM/EAI vendors Deployed in production
XPDL