Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

The BPEL eample example shows how perform to integrate the PXE BPEL Engine integration into with ServiceMix. Business Process Execution Language (BPEL) defines a notation for specifying business process behavior based on Web Services. PXE is a runtime component for executing processes defined by the BPEL4WS 1.1 specification and forthcoming WS-BPEL 2.0 OASIS standard. The 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 , which illustrates the BPEL example, is the example of travel agent airline ticketing system that offers online reservation reservations to its customers. When a customer requests to be booked for books a flight, the 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 receives the request. It The Binding Component then forwards the request via the NMR to the Airline Reservation System inside the PxeBpelEngine service container. The Airline Reservation System checks its database to see if it can still accomodate accommodate the request and formulate generates a response. After that it , the Airline Reservation system sends the response back to the Binding Component again via the NMR. The Binding Component then publish publishes it on the ticketing topic. The reserveTicket class is also a subscriber of the topic and thus receives the message. Whether the request is granted or not, the reply is outputed published to the customer.

The following diagram illustrates this:

...