Testing -ERP message in Q5 - IBM Websphere

Everything has been successfully configured, and the infrastructure is “up and running,” so now it is time to test our scenario and see transaction results in our Transaction Viewer and system logs.

This shows the steps that will occur when we trigger the scenario putting the ERP message in Q5.

Inbound flow steps for the scenario

Inbound flow steps for the scenario

Here is an explanation of the steps that are shown in this.The numbers correspond to:

  1. A message (flat file) is put on Q5 with RfhUtil, where the ERP_MQ Front SideHandler is listening.
  2. Writing a message in Q5 using RfhUtil

    Writing a message in Q5 using RfhUtil

  3. The message is grabbed by ERP_MQ FSH and the message enters in the MPG Policy ERP_Transformation_Policy where the transformation occurs that converts the Input Content to XML.
  4. After the message is transformed, it is sent via HTTP to the Banking Hub B2B Gateway Service, which is listening with its HTTP FSH.
  5. The message is wrapped in AS2 (including signing and encryption) and sent to Banking_Partner_B2BGW using the BankingPartner profile (AS3_2_bankingpartner destination on port 10081).
    Banking_Partner_B2BGW receives the AS3 message using
    Banking_Partner_AS3FSH ,which is included in it.
  6. An MDN is sent through 10082 to Banking_Hub_B2BGW.
  7. Banking_Partner_B2BGW verifies the message signature, deciphers it,and unwraps the message. Then, it is sent back through MQ to Q6.

Test results

After the completion of step 1, the rest of the steps are triggered within the device,and the processing finishes with a message in Q6. Let us examine the queue using the RfhUtil utility .

Browsing output messages in Q6 using RfhUtil

Browsing output messages in Q6 using RfhUtil

And, let us see our transaction in the Transaction Viewer.

Transaction Viewer showing transactions

Transaction Viewer showing transactions

If we examine the content in detail, you can see that Document type and Document IDs have been selected using the XML Format that we configured, and they are displayed in the Transaction Viewer.

Document type (Payment list) and Document ID (1138) details

Document type (Payment list) and Document ID (1138) details

If we want to examine the Header data,we can by clicking Show Headers (Figure below).

Showing AS3 Headers

Showing AS3 Headers

if we want to see any of the incoming or outgoing content, we click the Transaction Set ID that corresponds to our transaction, and a Document pop-up menu appears where you can select Content .

Showing content of the trading document using Transaction Viewer

Showing content of the trading document using Transaction Viewer


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

IBM Websphere Topics