Creating the XML_FlightQueryOut message flow

Use the following instructions to create the XML_FlightQueryOut message flow. For more detailed instructions, click the links provided at the end of each step.

To create and configure the XML_FlightQueryOut message flow:

  1. Create a new message flow called XML_FlightQueryOut.
    For instructions, see Creating a message flow in the IBM Integration Bus documentation.
  2. In the Message Flow editor, add and rename the nodes listed in the following table.
    For instructions, see Adding a message flow node in the IBM Integration Bus documentation.
    Palette drawers Node type Node name
    WebSphere MQ MQInput XML_FLIGHTQUERY_IN
    WebSphere MQ MQOutput XML_FLIGHTQUERY_FLIGHT
    WebSphere MQ MQOutput XML_FLIGHTQUERY_PASSENGERS
    WebSphere MQ MQOutput XML_FLIGHTQUERY_FAIL
    Routing AggregateControl RequestDetails
    Routing AggregateRequest RecordFlightRequest
    Routing AggregateRequest RecordPassengerRequest
  3. Connect the nodes together as shown in the following table.
    For instructions, see Connecting message flow nodes in the IBM Integration Bus documentation.
    To check that you have connected the nodes together correctly, see the diagram in About the XML_FlightQueryOut message flow.
    Node name Terminal Connect to
    XML_FLIGHTQUERY_IN Out RequestDetails
    Catch XML_FLIGHTQUERY_FAIL
    RequestDetails Out XML_FLIGHTQUERY_FLIGHT
    Out XML_FLIGHTQUERY_PASSENGERS
    XML_FLIGHTQUERY_FLIGHT Out RecordFlightRequest
    XML_FLIGHTQUERY_PASSENGERS Out RecordPassengerRequest
  4. Configure the node properties as shown in the following table. Accept the default values for all properties unless an alternative value is shown in the table.
    For instructions, see Configuring a message flow node in the IBM Integration Bus documentation.
    Node name Page Property Value
    XML_FLIGHTQUERY_IN Basic Queue name XML_FLIGHTQUERY_IN
    (This value is the local queue from which the message flow takes the message.)
    Input Message Parsing Message domain XMLNSC : For XML messages (namespace aware, validation, low memory use)
    (This value tells the integration node to use the generic XML parser.)
    RequestDetails Basic Aggregate name FLIGHTDETAILSAGG
    (This value must be unique in the integration node and must match the Aggregate Name property in the Aggregate Replies node in the XML_FlightQueryIn message flow.)
    Basic Timeout 120
    (This value tells the Aggregate Replies node in the XML_FlightQueryIn message flow how many seconds the integration node must wait for the replies before it passes the incomplete aggregated message to the timeout queue.)
    XML_FLIGHTQUERY_FLIGHT Basic Queue name
    (You are not required to specify the name of the queue manager because the queue is defined on the same queue manager as the integration node.)     		XML_FLIGHTQUERY_FLIGHT
    (This value is the local queue on which the message flow puts the message so that the XML_FlightQueryReply can get the message.)
    Request Request Select the check box to specify that this is a request.
    Request Reply-to-queue XML_FLIGHTQUERY_REPLIES
    (This value is the local queue on which the message flow puts the message so that the XML_FlightQueryReply can get the message.)
    RecordFlightRequest Basic Folder name FlightDetails
    (This value indicates where the Aggregate Replies node in the XML_FlightQueryIn message flow puts the information in the reply message.)
    XML_FLIGHTQUERY_PASSENGERS Basic Queue name
    (You are not required to specify the name of the queue manager because the queue is defined on the same queue manager as the integration node.)     		XML_FLIGHTQUERY_PASSENGERS
    (This value is the local queue on which the message flow puts the message so that the XML_FlightQueryReply can get the message.)
    Request Request Select the check box to specify that this is a request.
    Request Reply-to-queue XML_FLIGHTQUERY_REPLIES
    (This value is the local queue on which the message flow puts the message so that the XML_FlightQueryReply can get the message.)
    RecordPassengerRequest Basic Folder name PassengerDetails
    (This value indicates where the Aggregate Replies node in the XML_FlightQueryIn message flow puts the information in the reply message.)
    XML_FLIGHTQUERY_FAIL Basic Queue name
    (You are not required to specify the name of the queue manager because the queue is defined on the same queue manager as the integration node.)     		XML_FLIGHTQUERY_FAIL
    (This value is where the message flow puts the message if the processing fails.)
  5. Save the message flow.

You have created the XML_FlightQueryOut message flow, which is the aggregate fan-out part of the XML_FlightQuery message flow. The XML_FlightQueryOut message flow works with the XML_FlightQueryReply and XML_FlightQueryIn message flows to request and retrieve information about a specific flight and the passengers who have reserved seats on that flight.

Back to Building the Airline Reservations sample