1. PEtALS Enterprise Service Bus
h3p://petals.ow2.org

2. PEtALS JBI extension
• JBI specificaAon defines BC, SE, configuraAon,
management, message format…
• PEtALS extends the specificaAon to provide a
distributed Service Bus
• All the services are potenAally reachable by all
the services from all the PEtALS nodes
– This is an unified Distributed Service Bus.
– It is totally transparent from the consumer point
of view !

3. Distributed Service Bus
REST SOAP FTP BPEL
BC BC BC SE
PEtALS PEtALS
Registry Registry
REST SOAP FTP BPEL
BC BC BC SE
PEtALS
Registry

4. Service Engine (SE)
• Provide an internal technical service :
– BPEL processor
– XML transformaAon (XSLT)
– Content Based RouAng
– Rules with Jboss Drools
– Entreprise IntegraAon Pa3ern
– JSR181 with Axis2
– POJO
– …

5. Binding Component (BC)
• A Binding Component is used to
– Expose internal services as external ones
• For example, expose a rules service as a Web Service
– Access to an external Service
• For example, access to an external Web Service
• Its role is the message protocol adapaAon
– For example, expose an external EJB as Web
Service
• SOAP, REST, EJB, FILE, FTP, Mail, Database, …

6. Internal Endpoint acAvaAon
• An endpoint is acAvated by deploying a configuraAon
artefact to the component (BC or SE)
• This configuraAon artefact is a ZIP archive containing
– a XML file with some basic informaAon
• The Service Name
• The Interface Name
• The Endpoint Name
• A reference to the WSDL descripAon
• AddiAonal parameters (specific to component, ie BPEL process file
name, Drools file name…)
– The WSDL file (opAonal)
– AddiAonal resources like BPEL process file, Drools file…
• The acAvated endpoint is registered in the Technical Service
Registry and is now reachable by all the Service Bus
Services Consumers

7. Component Deployment
Comp
1. Deploy + Start
BC
Admin
2.Bind
Service

8. Endpoint AcAvaAon IllustraAon
SA
1. Deploy + Start
BC SE
3. Bind Admin
Service
2. Register Enpoints

9. Exposing/Consuming Services
• The SE provides a JBI Service
• The BC consumes the JBI Service and exposes
it to the outside WS
Client
http://localhost:8084/petals/services/BPELService
FTP BPEL SOAP
BC SE BC
PEtALS
Registry

10. Service OrchestraAon Sample
The Travel Service
Yahoo REST
Weather Service
Airline Web
Service WS
Client
Hotel EJB Service http://localhost:8084/petals/services/TravelService
REST EJB XSLT BPEL SOAP
BC BC SE SE BC
PEtALS
Registry

11. Agile Service OrchestraAon
• Now able to orchestrate not only Web
Services
– No ma3er of the service type, all are seen as JBI
Services from the orchestrator
– No ma3er of protocol transformaAon, it is the job
of the Binding Component
• Flexibility :
– Replace the hotel EJB service by a hotel REST
Service
– The BPEL declaraAon remains the same !

12. PEtALS ESB Monitoring
PEtALS Web GUI
Monitoring API
SOAP (SOAP, JMX)
BC
Fractal
Component A
Fractal
Monitoring Fractal
Service Component B Registry

13. PEtALS Monitoring (light version)
• Endpoints (Internal and External) and
Components are wrapped
• Wrappers collect and send data to the
monitoring service
• Monitoring Service persists, process,
aggregates, etc
• Monitoring Service expose an API (SOAP, JMX)