| By SOA News Desk |
Article Rating: |
|
| August 16, 2007 02:45 PM EDT |
Reads: |
9,751 |
Why does SOA need BPEL? The answer, according to Active Endpoints' Principal Architect Mike Pellegrini, is orchestration. The Business Process Execution Language isn't for creating Web services, it is for creating higher-level abstractions on top of those services.
BPEL is the Web services orchestration standard from OASIS defining a portable execution format.
BPEL is considered "programming in the large," Pellgrini explained, because it deals with higher-level constructs such as flow control and looping, processes that are long running (for instance, a request for a loan approval might be routed to the accounting department and sit there for days before being approved or denied), fault tolerance (it can be set up to start an alarm process if accounting does not respond to the loan request within a week), and it uses compensation instead of transactions (a transaction can't be kept open for the length of time needed in a long-running process, so, if a stage of a process fails, it has to be "fixed," not just rolled back).
BPEL is designed to fit naturally into the Web services stack, complementing the existing Web services specifications that are out there.
Active Endpoints, Pellegrini explained, created the open source ActiveBPEL Engine to generate interest in the BPEL standard and to help educate the community about BPEL.
Active Endpoints has also recently released ActiveBPEL for People, which extends BPEL to include people-oriented tasks, including roles and Web-based user interfaces.
Subscribe to SOA World Magazine Email News Alerts
Subscribe via RSS
