PUBLIC MARKS with tags workflow & bpel

Les spécifications BPEL [...] sont désormais supportées en version 1.1 par Workflow Foundation (WF)

BPEL, which has been designed specifically for defining business processes, supports typical interactions such as synchronous and asynchronous operation invocation, sequential and parallel flows, message correlations, fault and compensation handlers and activities triggered by events. Business processes often require human interactions as well.

XPDL is a way of moving a process from one design/simulation/analysis tool to another (about 30 tools support it today), whereas BPEL is about the nuts and bolts of sending messages from one location/service/system to another. XPDL is like XMI for business processes.

BPEL isn't about visibility, and it's not about change management, yet those are the central problems of business process management. BPEL as a technology is orthogonal to the problem of business process management. It's simply a new way to write code.

There recently has been a big realization that "Human BPM" is very important. IBM and SAP release their BPEL4People white paper. BEA buys Fuego, a notable human workflow vendor. Oracle prepares new human capabilities above (and possibly separate) from their BPEL engine. And Microsoft talks about their Workflow Foundation, which is also separate from their BizTalk EAI.

BPEL is an "execution language". XPDL is a process design format.

Open Source BPEL Server ActiveBPEL, LLC is an open source software organization that licenses and distributes the ActiveBPEL™ engine technology. The ActiveBPEL engine is a robust runtime environment that is capable of executing process definitions created to the Business Process Execution Language for Web Services (BPEL4WS, or just BPEL) 1.1 specifications.