converted to 1.6 markup
|No differences found!|
Welcome to Apache Agila Wiki
Agila is centered around Business Process Management, Workflow and Web Service Orchestration. It's composed of two specialized modules: Agila BPM and Agila BPEL.
Agila BPM is basically handling tasks and users who have to complete these tasks. It's a very flexible and lightweight workflow component.
Agila BPEL is a BPEL-compliant Web Services Orchestration solution. Here is a short description of what BPEL is good and bad for (from Paul Brown's presentation "BPEL for Programmers and Architects")
- BPEL is not workflow: there are no explicit abstractions for people, roles, work items, or inboxes in BPEL (among other things).
- BPEL is also not BPM: no specified data model for measurement, reporting, or management.
- BPEL is not integration: there is no explicit support for transformation, semantic interpolation, or specific protocols.
- BPEL is not all-encompassing: there are some patterns that are difficult to model with BPEL.
- BPEL (i.e., an implementation) abstracts the common, non-process-level concerns of business process execution.
- As a service-tier composition language, BPEL is a key ingredient in a service-oriented architecture.
- BPEL provides a deployment-level interface for higher-level tools (e.g., modeling).
- "Low-hanging" innovation does not create sustainable competitive advantage.
- Complexity will remain an unavoidable part of the enterprise technology landscape. Managing and minimizing that complexity will create leaders.
- Defining the organizational processes around BPEL, i.e., who uses BPEL and how, is of paramount importance to the role and success of service oriented architecture.
This wiki is powered by MoinMoin.