Apache ODE
| Developer(s) | Apache Software Foundation |
|---|---|
| Stable release | 1.3.5 / February 6, 2011 |
| Development status | Active |
| Written in | Java |
| Operating system | Cross-platform |
| Type | Workflow engine, Middleware |
| License | Apache License 2.0 |
| Website | http://ode.apache.org/ |
| Standard(s) | WS-BPEL, WSDL, SOAP, JBI |
Apache ODE (Apache Orchestration Director Engine) 'executes' or 'runs' one or more business processes which have been expressed in the Web Services Business Process Execution Language (WS-BPEL). It principally communicates with one or more Web services, sending and receiving messages, manipulating data and handling exceptions ('errors') as defined by any given process. The engine is capable of running both long and short living processes to coordinate all the services that make up a service or application (orchestration).
WS-BPEL itself is based upon the XML language and includes a number of ways in which business processes can be expressed. These include conditional clauses, repeating loops, calls to web services and the exchange of messages. Where interfaces with web services are required, it makes use of Web Services Description Language (WSDL) to express them. Messages can be handled in a flexible way by reading either part or all of the message into variables, which can then be used for onward communication.
The engine has two communication layers, with which it interacts with the outside world. :[1]
- Apache Axis2 integration layer: supports the communication over Web services.
- Layer based on the JBI standard: supports communication via JBI messages.
Features
- Side-by-side support for both the WS-BPEL 2.0 OASIS standard and the legacy BPEL4WS 1.1 vendor specification.
- Supports 2 communication layers: one based on Axis2 (Web Services http transport) and another one based on the JBI standard (using ServiceMix).
- Support for the HTTP WSDL binding, allowing invocation of REST-style web services.
- Possibility to map process variables externally to a database table of your choice.
- High level API to the engine that allows you to integrate the core with virtually any communication layer.
- Hot-deployment of your processes.
- Compiled approach to BPEL that provides detailed analysis and validation at the command line or at deployment.
- Management interface for processes, instances and messages.
Embedding
Apache ODE is embeded and an important part of the Jboss projects RiftSaw (WS-BPEL 2.0 engine) and also in the follow-up SwitchYard, which is a service delivery framework for service-oriented applications.
See also
- WS-BPEL
References
- ↑ "How to deploy an Axis2 Web service programatically in ODE during the initialization of ODE Runtime". http://ddweerasiri.blogspot.com/: Denis's Blog. Retrieved 2011-05-16. "Apache ODE (Orchestration Director Engine) executes business processes written following the WS-BPEL standard. It has two communication layers. One is Axis2 integration layer and the other one is based on JBI standard. Those integration layers are used by ODE BPEL Engine Runtime for interact with the outside world. Axis2 integration layer supports for communicate via Web Service interactions. JBI integration layer supports for communicate via JBI messages."
External links
| ||||||||||||||||||||||||||||||||
