All of the files that you require to run the Airline Reservations sample are supplied, but if you prefer to create the sample yourself use the following instructions.
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 of the information about the structure of the message is held within the message itself.
Before you can create a message flow, you must create a new Integration project. If you have not previously imported the sample name the Integration project XML Airline Message Flows. If you have previously imported the sample an Integration project called XML Airline Message Flows already exists, so you must choose an alternative name. The instructions in the following section assume that you have named the message flow Airline XML Messageflows. For more information, see Creating an Integration project in the IBM Integration Bus documentation.
You must also create an ESQL file in the Integration project that you created. The instructions in the following section assume that you have named the ESQL file message_flow_name, where message_flow_name is the name of the message flow. For more information, see Creating an ESQL file in the IBM Integration Bus documentation.
When you have created the Integration project, create each of the following message flows:
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.
To run the Airline Reservations sample you must create a database. For more information, see Setting up the database.
To run the XML_Airline message flows that you create, you must create the WebSphere MQ local queues that the message flows require. For more information, see Creating the WebSphere MQ queues.