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], a [Web console], 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.

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].

License

Petals ESB and its components are all licensed under the terms of the LGPL License.

Where can I get the source code?

The source code for Petals ESB and its components can be found on the OW2 Forge.