E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (20)
View Page History{section}
{column}
{column}
h1. What is Petals ESB?
h1. What is Petals ESB ?
[Petals ESB|http://petals.ow2.org] is an open-source Enterprise Service Bus (ESB) provided by the [OW2 Middleware Consortium|http://www.ow2.org].
ESB, and Petals ESB in particular, are generally related to Service Oriented Architectures (SOA).
ESB, and Petals ESB in particular, are generally related to Service Oriented Architectures (SOA).
[Petals ESB|http://petals.ow2.org] is an Open Source ([LGPL License|http://www.gnu.org/licenses/lgpl.html]) Enterprise Service Bus (ESB) provided by the [OW2 middleware consortium|http://www.ow2.org].
\\
More concretely, Petals ESB is a Java platform that can be used to interconnect heterogeneous systems, applications and services.
It acts as a mediation and a communication layer. Its architecture and the standards it supports make it a valuable solution for both integration and SOA projects.
More concretely, Petals ESB is a Java platform that can be used to interconnect heterogeneous systems, applications and services.
It acts as a mediation and a communication layer. Its architecture and the standards it supports make it a valuable solution for both integration and SOA projects.
Petals ESB is build with and on top of agile technologies such as:
* The Java Business Integration (JBI) v1.0 specification ([http://www.jcp.org/en/jsr/detail?id=208]). This is the Java standard for enterprise application integration. Note that in 2008, Petals ESB has been certified by SUN Microsystems as a valid JBI implementation.
* The FRACTAL Software Component Framework provided by the OW2 consortium ([http://fractal.ow2.org]). Fractal is a modular and extensible component model that can be used with various programming languages to design, implement, deploy and reconfigure various systems and applications, from operating systems to middleware platforms and to graphical user interfaces. On the Petals ESB point of view, all the container services (such as service registry, message router, message transporter, component installer etc...) are provided by the Fractal framework. This is a major feature which allows core developers to specialize a Petals ESB distribution by choosing the software components to be used for specific needs.
* The Java Business Integration (JBI) v1.0 specification ([http://www.jcp.org/en/jsr/detail?id=208]). This is the Java standard for enterprise application integration. Note that in 2008, Petals ESB has been certified by SUN Microsystems as a valid JBI implementation.
* The FRACTAL Software Component Framework provided by the OW2 consortium ([http://fractal.ow2.org]). Fractal is a modular and extensible component model that can be used with various programming languages to design, implement, deploy and reconfigure various systems and applications, from operating systems to middleware platforms and to graphical user interfaces. On the Petals ESB point of view, all the container services (such as service registry, message router, message transporter, component installer etc...) are provided by the Fractal framework. This is a major feature which allows core developers to specialize a Petals ESB distribution by choosing the software components to be used for specific needs.
Reusing monolithic applications by exposing them as services in the bus, enriching and plugging them with new services built on the latest standards is one possible usage of Petals ESB.
Other usages of Petals ESB are listed [here|Petals Usage].
Other usages of Petals ESB are listed [here|Petals Usage].
Petals ESB proposes a collection of Binding Components and Service Engines, that support various best of the breed SOA standards such as SCA, BPEL, XSLT, EIP...but also already proved communication standard such as HTTP, Mail, FTP. Reuse monolithic applications by exposing them as service in the bus, enrich them with new services built on the latest standards, plugged the services together on the Petals ESB, you compose any agile SOA applications that you want\!
\\
Petals ESB is build with and on top of agile technologies such as [Java Business Integration (JBI)|http://www.jcp.org/en/jsr/detail?id=208] and [the FRACTAL Software Component Framework|http://fractal.ow2.org] provided by the OW2 consortium. Note that in 2008, Petals ESB was certified by SUN Microsystems as a fully-compliant JBI implementation.
Petals ESB is build with and on top of agile technologies such as [Java Business Integration (JBI)|http://www.jcp.org/en/jsr/detail?id=208] and [the FRACTAL Software Component Framework|http://fractal.ow2.org] provided by the OW2 consortium. Note that in 2008, Petals ESB was certified by SUN Microsystems as a fully-compliant JBI implementation.
\\
Petals ESB is made up a kernel (also called the container) and of extensions (known as Petals components).
These components support various best of breed SOA standards such as SOAP, BPEL, SCA, XSLT (among other ones), but also already proved communication standards such as HTTP, Mail, FTP, etc.
This organization makes Petals an extensible platform, that can be upgraded with the needs.
{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
Petals ESB is made up a kernel (also called the container) and of extensions (known as Petals components).
These components support various best of breed SOA standards such as SOAP, BPEL, SCA, XSLT (among other ones), but also already proved communication standards such as HTTP, Mail, FTP, etc.
This organization makes Petals an extensible platform, that can be upgraded with the needs.
{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
Petals ESB comes with a set of useful tools from development to exploitation. These tools are supported on 2 GUI axes, the Eclipse Studio and Web applications. Others tools around Ant, Nagios for example are proposed.
h1. Features
Petals ESB offer several and various features.
We here list the main ones:
* *Distributivity:* Petals ESB is distributed platform, one instance of the application being deployable on a machine and several machines being able to communicate together.
* *Guaranteed Message Delivery:* a message being sent to a service will always be delivered. If the service is off-line, the message will be either stored, or sent to an equivalent service.
* *Message Routing:* the effective message target can be chosen at runtime in function of several criteria.
* *Robustness:* forwarding messages are persisted. In case of incident, the platform can restore its state and reemit messages that were not processed.
* *Respect of standards:* Petals ESB is built with and upon standards. This is true for both the container and the component features.
* *Monitoring:* the content and the properties of the messages that transit can be monitored.
* *Extensibility:* with its component-based architecture, it is possible to extend, update and modify the platform dynamically.
* *Tools:* that may not sound like a feature for the platform, but Petals ESB is completed by several tools, including a [development environment|petalsstudio:Home], a [Web console|webconsole:Home], a [governance solution]petalsmaster:Home], a Maven plug-in, administration ANT scripts and many more. These different tools target various project actors and profiles, making it a complete suite.
We here list the main ones:
* *Distributivity:* Petals ESB is distributed platform, one instance of the application being deployable on a machine and several machines being able to communicate together.
* *Guaranteed Message Delivery:* a message being sent to a service will always be delivered. If the service is off-line, the message will be either stored, or sent to an equivalent service.
* *Message Routing:* the effective message target can be chosen at runtime in function of several criteria.
* *Robustness:* forwarding messages are persisted. In case of incident, the platform can restore its state and reemit messages that were not processed.
* *Respect of standards:* Petals ESB is built with and upon standards. This is true for both the container and the component features.
* *Monitoring:* the content and the properties of the messages that transit can be monitored.
* *Extensibility:* with its component-based architecture, it is possible to extend, update and modify the platform dynamically.
* *Tools:* that may not sound like a feature for the platform, but Petals ESB is completed by several tools, including a [development environment|petalsstudio:Home], a [Web console|webconsole:Home], a [governance solution]petalsmaster:Home], a Maven plug-in, administration ANT scripts and many more. These different tools target various project actors and profiles, making it a complete suite.
h1. Software and Hardware Requirements
Petals ESB being a Java platform, it is cross-platform. It is regularly used on Linux, Red Hat and Windows platforms.
As a Java application, you imperatively need a Java Virtual Machine to run it. More precisely, you need a JDK 6.
More details about Software and Hardware requirements are given in the [installation guide|System Requirements].
As a Java application, you imperatively need a Java Virtual Machine to run it. More precisely, you need a JDK 6.
More details about Software and Hardware requirements are given in the [installation guide|System Requirements].
h1. License
Petals ESB and its components are all licensed under the terms of the [LGPL License|http://www.gnu.org/licenses/lgpl.html].
h1. Where can I get the source code?
{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
The *source code* for Petals ESB and its components can be found on [the OW2 Forge|http://forge.ow2.org/plugins/scmsvn/index.php?group_id=213].