Page History

The BPEL eample shows how perform PXE BPEL Engine integration into ServiceMix. PXE is a runtime component for executing processes defined by the BPEL4WS 1.1 specification and forthcoming WS-BPEL 2.0 OASIS standard. PXE BPEL engine uses JMX to provide management and introspection functionality. Business Process Execution Language (BPEL) defines a notation for specifying business process behavior based on Web Services.

A hypothetical business scenario: An travel agent airline ticketing system offers online reservation to its customers. When a customer requests to be booked for a flight, reserveTicket class of the online ticket reservation system publishes its request to the ticketing topic. The Binding Component which is capable of communicating both to the external reserveTicket class and the Airline Reservation System, is a subscriber to the ticketing topic and thus recieves the request. It then forwards the request via NMR to the Airline Reservation System inside the PxeBpelEngine service container. The Airline Reservation System checks its database if it can still accomodate the request and formulate a response. After that it sends the response back to the Binding Component again via NMR. Binding Component then publish it on the ticketing topic. reserveTicket class is also a subscriber of the topic and thus receives the message. Whether the request is granted or not, reply is outputed to the customer

ServiceMix is an Emterprise Service Bus (ESB) that is based on the Java Business Integration (JBI) standard JSR 208. The JBI-based design specifies a standards-based pluggable architecture with a JVM-based runtime component called the Normalized Message Router (NMR). The Basic example demonstrates how applications communicate via the ServiceMix ESB, and the role that the NMR can play in that communication. Similar techniques could be used to plug any external ¹ application or service into ServiceMix (e.g. SAP, Peoplesoft, spreadsheets, POJOs, Webservices and EJBs) and allow it to communicate with other external applications or components using ServiceMix itself.

A hypothetical business scenario, which extends the Basic Example, is that of a department store distributor. This distributor sells products from multiple wholesalers (suppliers) to various retailers (customers). The distributor presents a common interface for product ordering to each of its department store customers. However, the distributor must work with a different ordering interface for each wholesale suppliers for the products they are buying.

Using an ESB, the distributor has developed a number of components to receive department store orders and then dynamically route and transform these orders to the appropriate wholesaler. The order processing flow is described as follows:

...

.

The following diagram illustrates this:

...

...