About the Managed File Transfer sample

WebSphere Message Broker implements managed file transfer using WebSphere MQ File Transfer Edition.

The scenario is used typically in a retail environment.

FTEScenario

  1. At the end of each day, an application at the branch outlet sends an XML file to headquarters (HQ). The XML file contains details of the daily product sales.
  2. HQ receives the file and splits the file into individual product records.
  3. At HQ, an application determines which products need replenishing.
  4. HQ sends the file back to the branch outlet with details of the daily product delivery.

The Managed File Transfer sample uses the following nodes:

These nodes can be used together or independently. The sample has four message flows:

  1. Branch2HQDriver.msgflow simulates an XML file being produced by an end-of-day sales application at the branch outlet. The file has details of the daily product sales, and is sent to HQ by Websphere MQ File Transfer Edition, see Branch sends details of daily sales to HQ.
  2. FTEInputBranch2HQMFlow.msgflow receives the XML file and splits it up into individual XML records. The records are put on a WebSphere MQ queue ready for the HQ stock provisioning application, see HQ receives the file.
  3. HQProcessingDriver.msgflow simulates the HQ stock provisioning application receiving the XML records from the WebSphere MQ queue. The flow determines which products need replenishing and puts the records onto a WebSphere MQ queue, see HQ application constructs the response message.
  4. FTEOutputHQ2BranchMFlow.msgflow receives the XML records and puts them into a single file, which is sent back to the branch outlet with details of the daily product deliveries, see HQ sends the file to the branch.

Branch sends details of daily sales to HQ

branch2hqflow

The application of the branch outlet produces an XML file, showing details of products sold that day. An FTE agent sends the file to HQ.

  1. An MQInput node receives an XML message containing the details of three products with quantity details.
  2. A Compute node extracts the branch number from the MQMD header, and stores it in the local environment.
  3. An FTEOutput node transfers the file.

HQ receives the file

fteinputflow

HQ receives the file through the FTEInput node. The node splits the file into individual product records.

  1. When a message is ready for transfer, the broker FTE agent gets a notification to tell the FTEInput node to pick up the message.
  2. If the broker or agent are stopped or end abnormally, the messages are passed through a Resequence node to prevent duplication of messages.
  3. An MQOutput node then writes each message to a WebSphere MQ queue to be processed.

HQ application constructs the response message

hq2branchflow

The HQ stock provisioning application constructs a response message, with details of products to send to replenish the branch outlets.

  1. An MQInput node receives XML-based messages containing the details of a single product with quantity details.
  2. A Compute node changes the details of the selected product information, as indicated in the ESQL.
  3. An MQOutput node puts the messages onto a WebSphere MQ queue.

HQ sends the file to the branch

fteoutputflow

HQ sends the reply to the branch outlet by using WebSphere MQ File Transfer. The reply contains details of items to deliver.

  1. An MQInput node receives an XML message for every product that is being replenished.
  2. The branch number is used to form the filename for transmission, and the branch number is stored in the local environment.
  3. A Compute node extracts the branch number. The branch number, which is stored in the local environment, forms the filename.
  4. When the XML message indicates the end-of-data for the branch, the FTEOutput node writes the resulting messages to the file.
  5. The broker FTE agent transfers the file to the branch.

Back to sample home