Differences between revisions 28 and 29
Revision 28 as of 2006-02-18 17:36:44
Size: 7188
Editor: AlanCabrera
Comment:
Revision 29 as of 2009-09-20 23:05:21
Size: 7188
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

PROJECT PROPOSAL

Ode - Orchestration Director Engine

"A lyric poem of some length, usually of a serious or meditative nature and having an elevated style and formal stanzaic structure". - American Heritage Dictionary

We are proposing an orchestration service that implements the WS-BPEL specification. The implementation will also support Message/Event to process correlation

The project proposal includes development of an orchestration engine abstraction to standard externally defined interfaces/bindings. The interface implementations and/or bindings will enable the orchestration service to be plugged into various service bus or component architectures.

RATIONALE

For a complete SOA stack, course-grained, long lived, service orchestration is an important aspect of service interaction. WS-BPEL is the standard description language for describing this level of service interaction. While there is a lot of ongoing effort in Apache towards solving the assembly and bus architecture issues of SOA, the higher level orchestration integration aspect could be better served.

INITIAL SOURCE

The initial source for Ode originates from a Sybase donation and the PXE BPEL 2.0 engine from Intalio.

The Sybase donation generically implements a superset of the academically recognized workflow patterns that are a superset of WSBPEL yet adhere to specific WSBPEL v1.1 language constructs. The initial source contribution does not require any WSBPEL extensions and is opaque with respect to the orchestration process context types. The initial source fully implements the BPEL v1.1 specification however there are some things to do:

  1. Implement specific service bus plug-ins.
  2. Implement a non-J2EE persistence mechanism for stateful processes running outside a J2EE container.
  3. Port to BPEL 2.0 once the specification is public.

The Intalio PXE BPEL 2.0 engine is currently licensed under the CPL open source license, and has been integrated into third-party products/projects such as Sun's Java Studio Enterprise and Apache ServiceMix.

RESOURCES TO BE CREATED

  • SVN Repository
  • Jira
  • Mailing Lists
  • Official Build Systems

ALIGNMENT

We propose growing the Apache SOA stack through integration with ServiceMix, Axis, Tuscany, Celtix, etc ...

The proposed implementation will solely focus on service orchestration. We will implement the appropriate plug-in points for a specific ESB or component architecture. This would include exposing BPEL definitions as a service, enable the consumption of services by a BPEL process and exposure of BPEL management services.

AVOIDING THE WARNING SIGNS

Orphaned products:

The core of the donated code is used within a commercially viable product and receives constant feedback. The project will be actively supported both by the current committers and those in the community actively seeking to leverage orchestration with the SOA stack. The BPEL 2.0 specification is a diverse and active community and we anticipate continued interest in the orchestration of Web Services and integration with other Apache projects.

The Eclipse foundation has formed a BPEL tooling project (http://www.eclipse.org/bpel/) that will help visualize service orchestration and add to service orchestration interest.

Inexperience with open source:

Many of the current committers have experience working with open source projects and communities and the leaders of this project are long time ASF contributors. We do not expect any difficulty in executing under normal meritocracy rules.

Homogenous developers:

The initial contributions are developed by Sybase and Intalio employees but there is a strong support of developers wishing to work on the code from the current Geronimo, ServiceMix and Agila projects as well as developers from various companies: Envoi Solutions, IBM, Intalio, LogicBlaze, Sybase, Unity Systems, Virtuas, and WSO2...

No ties to other Apache products:

We are anticipating that the service orchestration engine will be used within a larger SOA stack (i.e. ServiceMix, Tuscany, Synapse). To that end we will actively work with other projects to define and implement the appropriate plug-in points/bindings/abstractions orchestration. The default standards based plugin architecture for integration components is JBI (JSR 208) which we will be tackling first. Other kinds of plugins could be created over time.

For QoS features the Ode project will leverage Geronimo backbones (transaction management, security, threading).

COMMITTERS

The following individuals have expressed interest in participating as committers:

PROPOSED APACHE SPONSOR

We kindly request the Apache Incubator PMC to accept this project.

MENTORS

These individuals will participate as Incubator Mentors

  • Paul Fremantle
  • Geir Magnusson Jr.
  • Davanum Srinivas
  • James Strachan

OdeProposal (last edited 2009-09-20 23:05:21 by localhost)