Testing with POST tool - IBM Websphere

For our testing, we will use cURL as the power on system test (POST) utility, but you can use any POST tool that is available on the Internet.

HTTP Headers need to be included in the POST Request. You can add them to the cURL request with the -H parameter followed by the headers separated by the (;) semicolon.For our case, we need Content-type, Type,and Boundary http headers.

Example - cURL script that we use to test the scenario with important headers (in Bold) to be set

Important:When testing this scenario,make sure that there are spaces between each part of the message. A is required for each of the specific parts.

you can see the steps that will occur when we trigger the scenario by posting a message with cURL to the SWA MPGW.

SOAP Messages with Attachments testing flow

SOAP Messages with Attachments testing flow

Here is an explanation of the high-level steps. The numbers in Figure below correspond tothese numbered steps:

  1. The SOAP Messages with Attachments message is posted to the DataPower device using cURL, where SWA_http_FSH Front Side Handler is listening on port NN.
  2. The SOAP Messages with Attachments Message is received by the http FSH,the SOAP content is verified as valid SOAP,and the message comes into the policy SWA_Policy.
  3. Inside the SWA_Policy, the attachment is stripped and then wrapped with AS2 headers using the information coming in the SOAP payload. And then, the message is routed to the appropriate back end,using the mpg-routing-test.xsl inside the Route action and the b2b-routing.xml file.
  4. The new payload is sent to Partner_Binary B2BGW. This service receives the AS2 message using PartnerBin_as2_fsh front side handler.
  5. The payload is processed by the B2B Gateway Service and routed to the back-end server.If you are using the Partner Binary B2B Gateway Service, its destination is an MQ queue.

Test results

To see the test results, you can look at the SWA_MPG probe tocheck that all the headershave been generated successfully and that the attachment was stripped correctly.

Probe of our test results

Probe of our test results

This shows the Input content that represents what comes into the device.

Input context coming from our test results

Input context coming from our test results

This shows the headers that we attached during the process in the Output content view of the Probe,which represent what leaves the device after all the processing.

Output context coming from our test results

Output context coming from our test results


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

IBM Websphere Topics