About the XML_PassengerQuery input messages

The XML_PassengerQuery input messages are supplied so that you can run the XML_PassengerQuery message flow to request information about the reservations stored in the user database. There are two XML_PassengerQuery input messages. The first input message contains only a reservation number, and so requests information about only that specific reservation. The second input message contains the name of a passenger, and so requests information about all the reservations made by that person.

The two XML_PassengerQuery input messages are identical in structure and vary only in their content.

Input message 1 (passengerquery1.mbtest) contains the following data:

<PassengerQuery>
   <ReservationNumber>CA937200305253</ReservationNumber>
   <FirstName></FirstName>
   <LastName></LastName>
</PassengerQuery> 

Input message 2 (passengerquery2.mbtest) contains the following data:

<PassengerQuery>
   <ReservationNumber></ReservationNumber>
   <FirstName>Mary</FirstName>
   <LastName>Smith</LastName>
</PassengerQuery>

Compare the input messages with the model in the following diagram. Notice that input message 1 contains values in the ReservationNumber field but the FirstName and LastName fields are empty, while input message 2 contains values in the FirstName and LastName fields but not in the ReservationNumber field. You can also read a textual description of the message structure.

Look at the ESQL in Creating the XML_PassengerQuery message flow. See how the message flow navigates the message to certain elements in the tree. For example:

InputRoot.XML.PassengerQuery.FirstName

For more information, read about XML messages in the WebSphere Message Broker documentation. Also take a look at the XML_PassengerQuery message flow.

Main Page icon   Back to About the Airline Reservations sample