1. MQFTE source agent receives the transfer and sends the file to the destination agent which shares queues with DataPower
2. Destination agent places file data as one or more messages in a group.
3. MQFTE front-side handler consumes message(s) from the queue, reassemble the message if there is more than one segments, and sends the data to the external partner
© 2011 IBM Corporation 45
Introduction
MQ FTE Overview
DataPower File handling Overview
File transfer scenarios with DataPower / MQ FTE
© 2011 IBM Corporation
Appliance
Agent
...
MQ queue : FTE2DP FTE Agent : APC QMGR : QMPC
© 2011 IBM Corporation
Appliance
Agent
...
MQ queue : FTE2DP FTE Agent : APC QMGR : QMPC
© 2011 IBM Corporation 48
MQFTE Source Agent can optionally configure the following metadata when integrating
with XB60.
When set, B2B Gateway will use these information to match the right partner profile settings.
•
DPMQFTESenderID : the business ID of internal partner•
DPMQFTEReceiverID : the business ID of external partner© 2011 IBM Corporation
Appliance
Agent
...
MQ queue : FTE2DP FTE Agent : APC QMGR : QMPC
© 2011 IBM Corporation 50
The Queue manager that host the shared queue The queue where we retrieve the message
© 2011 IBM Corporation 51
Partner File Transfer
Sender SourceAgent NetworkMQFTE DestinationAgent
Appliance
Get Queue
DataPower portion of transfer MQ File Transfer Edition portion of transfer
Logical flow of data
1. MQFTE source agent receives the transfer and sends the file to the destination agent which shares queues with DataPower
2. Destination agent places file data as one or more messages in a group. 3. MQFTE front-side handler consumes message(s) from the queue
4. Error happens in transaction processing and MQFTE front-side handler rolls the transfer back and. Go back to step 1 to retry the transfer.
5. If the number of retries reaches the “backout threshold”, then MQFTE front-side handler will send the transfer to the “backout queue”.
1
2
3
4 (error)
Backout Queue
© 2011 IBM Corporation
Agent Network Agent
Appliance
...
MQ queue
© 2011 IBM Corporation
Agent Network Agent
Appliance ... MQ queue dpmqfte://FTEWA/? RequestQueue=DP2FTE&DestAgent =APC& DestQM=QMPC&DestFile=testcompl ete.xml Network
© 2011 IBM Corporation 54
Mandatory
– DestAgent : the destination agent in MQFTE network that will ultimately receive the file
– DestQM : the destination queue manager the source agent should send the messages to
– DestFile : the filename to use when the destination agent need to store the received
messages into file.
– Unique filename is supported.
Optional
– SenderID : the business ID of sender (e.g. external partner )
– ReceiverID : the business ID of receiver (e.g. internal partner)
– ContentType : the content type of the message payload
Example :
– dpmqfte://QM_Demo/?
© 2011 IBM Corporation
Agent Network Agent
Appliance ... MQ queue agent="${DPMQFTEDestinationAgent}" QMgr="${DPMQFTEDestinationQM}" <file>c:\temp\$ {DPMQFTEDestinationFile}</file>
FTE Agent : AWA QMGR : FTEWA
© 2011 IBM Corporation 57
1. Outbound gateway sends a B2B message to inbound gateway
2. The DataPower appliance writes data to an MQ queue as one or more messages in a group. The message ID assigned to the first message in the group becomes the Integration ID. Other information
can be passed in the RFH 2 header of the first message
3. FTE consumes the group of messages and uses the information present in the first message in the group to route the data to a back end system, where it is written as a file
4. B2B Viewer of the outbound gateway retrieve the transaction metadata from the MQFTE Logger Database
Back-end System
Agent Network Agent
Appliance
MQ queue
DataPower portion
of transfer MQ File Transfer Edition portion of transfer
Outbound GW Inbound GW MQFTE Logger 4
© 2011 IBM Corporation 58
A new column to store the integration ID which could be used to correlate a B2B Transaction with a backend transaction
For MQFTE integration, the integration ID maps to the “transfer ID” of MQFTE network
For inbound, the integration-ID is the Message ID of first message we sent to the shared queue
For outbound, the integration-ID is the Message ID of the first message we received from the shared queue
© 2011 IBM Corporation 59
A pop-up to display the MQFTE metadata when the integration-id is clicked ( for MQFTE- related transaction only)
Depending on weather the transaction is inbound or outbound, the popup window will show different metadata
© 2011 IBM Corporation Integration between the B2B appliance and backend application is over WebSphere MQ
instead of a shared file system.
Files transferred between the B2B appliance and MQ FTE can be correlated using the integration ID from MQ; this ID can also be seen in the B2B Viewer.
The combined B2B messaging flow through the B2B appliance and file transfer flow through MQ FTE can be viewed through the B2B Viewer on the appliance. This provides the user with an end-to-end view of the file transfer.
File transfers can be set up to occur at specified times or dates, or repeated at specified intervals. File transfers can also be triggered by a range of system events, such as new files or updated files.