Building the Airline Reservations sample

All the files that you need to run the Airline Reservations sample are supplied. However, you can build the Airline Reservations sample yourself using the Message Brokers Toolkit.

You do not create a message set for the Airline Reservations sample because the message flows are designed to be run with self-defining XML messages. In a self-defining, or generic, XML message, all the information about the structure of the message is held within the message itself.

The message flow project and ESQL file

Before you can create any of the message flows, you must create a new message flow project, and an ESQL file in the project: For more information, see Creating a message flow project and Creating an ESQL file in the WebSphere Message Broker documentation. The instructions assume that you have named the message flow Airline XML Messageflows. You can give the ESQL file any name.

The message flows

When you have created the the message flow project, see the following topics for instructions about how to create each message flow:

Note that, at run time, the XML_FlightQueryOut, XML_FlightQueryReply, and XML_FlightQueryIn message flows function as a single message flow, which is referred to in this documentation as the XML_FlightQuery message flow.

The database

To run the Airline Reservations sample, you must create a database containing two tables, one of which is populated with sample data. The instructions assume that you are using DB2 Universal Database and a script is provided to create and populate a DB2 database for the Airline Reservations sample. For instructions, see Creating and populating the database.

The WebSphere MQ queues

To run the XML_Airline message flows that you create, you must create certain WebSphere MQ local queues. For instructions, see Creating the WebSphere MQ queues.

Main Page icon   Back to sample home