PUBLIC MARKS with tag bpel

"BPML was designed as a formally complete language, able to model any process, and, via a BPMS, deployed as an executable software process without generation of any software code. This is not possible with BPEL, since BPEL is not a complete process language."

Orchestra is a complete solution to handle long-running business processes orchestration. It is based on the OASIS standard BPEL (Business Process Execution Language). It includes a powerful BPEL Engine and all the related graphical tools to design, admin

BPEL provides a broadly adopted process orchestration standard supported by many vendors today and used to define business processes that orchestrate services, systems, and people into end-to-end business processes and composite applications

Human workflow is nothing more than a specific process pattern, and BPEL is largely sufficient to support it. Anyone telling you that BPEL does not support workflow is lying to you, and the best evidence for it are Intalio’s and Oracle’s products.

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

Des tonnes d'infos intéressantes sur SOA et les Web Services, par Pierre "Orchestra Networks" Bonnet

What is BPEL? What is it Good For? How does it work? What does it look like?

Workbench does not support BPEL and lacks process simulation capabilities, but its process-orchestration capabilities hit the mark.

eClarus Business Process Modeler for SOA Architects™ is a process modeling and services integration toolset which plugs into the Eclipse development framework. It delivers Roundtrip Engineering between BPMN and BPEL.

simple BPEL toolkit that a beginner can use to get familiar with

BPEL is fine for developers that are looking to link XML Web services, but may not be as effective for business users within the enterprise at large, who are working with all sorts of local objects, legacy systems and data types.

This SearchWebServices.com learning guide introduces you to Business Process Execution Language for Web services, or BPEL4WS. In this BPEL learning guide, you'll find articles, tips, expert advice, white papers and more that will explain how BPEL fits into the world of Web services.

Learn advanced BPEL concepts and best practices for development, deployment, and administration from the architects implementing them in real-world applications.

ActiveGrid est un environnement de réalisation d’applications WEB totalement intégré qui repose entièrement sur les standards XML les plus récents : BPEL, XForms, WSDL, XML Schema, XACML. L’offre d’ActiveGrid est composée d’un builder et d’un server, tout ça dans une architecture LAMP (le P devant se comprendre essentiellement pour Python).

ActiveGrid Studio makes it easy to create rich, interactive Web 2.0-style applications that integrate your existing databases, applications, and services. The ActiveGrid Studio offers graphical editors and wizards and is based completely on standard XML files so there is no code generation or proprietary metadata.

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.

The first part in this series of articles on BPEL4WS (Business Process Execution Language for Web Services) explains BPEL basic concepts, BPEL processes, and BPEL constructs. A sample BPEL process is provided. More advanced topics are covered in subsequent articles.

ActiveBPEL™ Designer is an integrated visual toolset for rapidly creating, testing and deploying composite applications based on the BPEL (Business Process Execution Language) standard. ActiveBPEL Designer is an Eclipse Ready™ technology that combines intuitive BPEL authoring tools with an embedded version of the ActiveBPEL engine technology, and is targeted at SOA architects, process designers, and Web services application developers.

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.