So far through the earlier parts of this example, we have created a sequential process
to invoke NorthAir Web Service. This process consists of storing and sending
itineraries to a JMS physical destination. Ideally, updating the partner airlines
repository is independent of itinerary processing. Despite of failed reservations, we
update the data store for the purpose of a waiting list (Of course without a confirmed
reservation ID).
UpdateItinerary sequence is introduced as a flow branch to process itinerary
branch, so both the sequences work in parallel. This part also shows how as part of
the UpdateAirlines sequence, we send the itinerary information to a travel agent's
FTP Server. Uploading itinerary information to an FTP server is done through an
FTP binding component.
Chapter 10
[ 253 ]
Whenever a request for reservation is made, the NorthAir Web Service is invoked
and the itinerary data is updated in the SouthAir database. Also, the itinerary
information is updated in the file system using the JBI file binding component. This
file can be constantly monitored by an external process. Now the itinerary data is
sent to EastAir's JMS Queue. EastAir's JMS Queue Listener can get the itinerary
information for further processing. The BPEL process also uploads the guest itinerary
to a remote FTP server of a travel agent or any AirAlliance partner.
Pages:
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222