Jump to content

Apache ODE

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Rjpgomes (talk | contribs) at 11:10, 26 September 2011. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Apache ODE
Developer(s)Apache Software Foundation
Stable release
1.3.5 / February 6, 2011 (2011-02-06)
Repository
Written inJava
Operating systemCross-platform
Standard(s)WS-BPEL, WSDL, SOAP, JBI
TypeWorkflow engine, Middleware
LicenseApache License 2.0
Websitehttp://ode.apache.org/

Apache ODE (Apache Orchestration Director Engine) is a WS-BPEL compliant Web service orchestration engine. It organizes web services calls following a process description written in the BPEL XML grammar.

The engine has two communication layers:[1]

  • Apache Axis2 integration layer: supports the communication over Web services.
  • Layer based on the JBI standard: supports communication via JBI messages.

These layers are used to interact with the outside world.

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.

References

  1. ^ "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. {{cite web}}: External link in |location= (help)

See also