|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (11)
View Page History{hide-from:anonymous}
h2. The Service Oriented Architecture FIXME
{hide-from}
h1. Petals ESB, the Enterprise Service Bus
Beyond the inherent improvments of an ESB over traditional EAI solutions, Petals ESB uses a best-of-breed approach and open source development model to distinguish from other ESB solutions, bringing essential features.
Beyond the inherent improvments of an ESB over traditional EAI solutions, Petals ESB uses a best-of-breed approach and open source development model to distinguish from other ESB solutions, bringing essential features.
h23. Natively Distributed Architecture
Most of EAI and ESB solutions are based on a centralized architecture. This choice brings simplicity of configuration and maintenance. One risk however is the great loss the company would sustain in case of serious problem with the middleware.
- inherent load balancing.
h23. Light & Powerful
Petals ESB is entirely modular, making it a light platform, running without application server. Numerous components are already available for data exchange (FTP, SOAP, REST, POP...) and data manipulation (POJO, Quartz, XSLT, Talend...)
Using notifications service engine, Petals View allows easy monitoring configuration, so that end business users can watch their business processes and analyse their efficiency.
h23. Standard and Open Source
Petals ESB is one of the few to be fully compliant with the Java Business Integration specification. It makes full use of standards protocols.
As an open source product, you can freely adapt it to fit your need, be it through a new component or container adaptation, or ask any expert to do it for you, without being bound to Petals Link (although we are probably the finest experts on these matters hehe).
h23. Ease of Use
Petals ESB is bundled with a [Web Console|webconsole], allowing graphical administration of services and nodes.
The container, components and services are also facilitated, with [Petals Studio|petalsstudio]'s wizards and code control.
{hide-from:anonymous}
h1. Petals ESB Use-cases FIXME
h2. Typical Use cases (?)
{hide-from}
h1. Petals ESB Use-cases FIXME
h2. Typical Use cases (?)
{hide-from}
{show-to:user=llacote}
h1. Petals ESB Use-cases
h2. Typical Use cases
- capacité d'intégration pragmatique dans le système, trois cas principaux.
- intégration
- intégration