Testing the binary FTP multi-step use case - IBM Websphere

Now, we perform a typical end-to-end test scenario outlining the message flow from the
Partner back-end application to the Hub back-end application.

FTP and Binary message flow

FTP and Binary message flow

The numbered steps correspond to the numbers:

  1. The binary message is placed on queue Q14 using the WMQ utility, RfhUtil.
  2. RfhUtil binary message

    RfhUtil binary message

  3. The message is received by the MQ FSH. The stylesheet b2b-partner-routing.xsl is invoked and the Sender, Receiver, and document type variables are set for routing to the HubBinary MPGW service.
  4. The message is sent over FTP to the HubBinary MPGW using the destination
    HubBin_FTP (defined in the HB_Ext partner profile).The message is received by the HubBinary_ftp_fsh FSH object on the HubBinary MPGW.
  5. B2B Transaction Viewer showing message transactions from MQ to FTP

    B2B Transaction Viewer showing message transactions from MQ to FTP

  6. The message is routed from the HubBinary MPGW to the proper MQ queue, in this case, Q13.
  7. HubBinary Debug Probe showing routed FTP message

    HubBinary Debug Probe showing routed FTP message


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Websphere Topics