BPEL process

This view shows the BPEL constructs that are used to implement the travel booking process in Business Process Choreographer.

 

step1 Receive activity
The Receive activity starts the travel booking process. The message sent to the process contains the required information in order to be able to perform the travel reservations, for example the destination and the day of departure.

step4 Data Maps
Data mapping in the travel booking process is done with Assign activities. The input variable for each invoke activity must be initialized and set before the invoke.

step4 Credit card check
The CheckCreditCard activity checks whether the given credit card information is complete and valid. The activity is implemented in an external Java class, and its methods are invoked by the travel booking process (the same applies for the CheckFlightReservation, CheckHotelReservation, and CheckCarReservation activities).

step4 Fault handling
If the credit card number provided by the customer is not valid, the Java implementation class of the CheckCreditCard activity throws an exception. This exception is caught in the BPEL process by a fault handler, which creates a fault message with the error information. This fault message is returned with the reply message and the travel booking process is ended.

step4 Flight reservation
The CheckFlightReservation activity performs the booking of the flight.

step4 Hotel reservation
The CheckHotelReservation activity performs the booking of the hotel.

step4 While loop
The While loop repeats the CheckCarReservation activity until the reservation of a car is finished successfully.

step4 Reply activity
Finally, is is checked whether the the flight, hotel and car have been booked successfully, and a reply message is created accordingly. If the travel booking was successful, the reply message contains a confirmation number.

Non-interruptible process
The travel booking process runs in one transaction. All invoke activities call synchronous methods.

Travel booking process