The XML_PassengerQuery input messages are supplied so that you can run the XML_PassengerQuery message flow to request information about the reservations that are stored in the user database. Two XML_PassengerQuery input messages are provided. The first input message contains only a reservation number, and therefore requests information about only that specific reservation. The second input message contains the name of a passenger, and therefore requests information about all of 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. Input message 1 contains values in the ReservationNumber field but the FirstName and LastName fields are empty. Input message 2 contains values in the FirstName and LastName fields but not in the ReservationNumber field. See also Structure of the XML_PassengerQuery input messages.
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.XMLNSC.PassengerQuery.FirstName
For more information, see Working with XML messages in the WebSphere Message Broker documentation. See also About the XML_PassengerQuery message flow.