The DataPower gateway’s Web Services Management (WS-M) enables payload capture of DataPower services (WSP, MPGW) as well as API-Connect v5/v5c APIs.

The following services are supported:

1. Web Service Proxy

2. Multi-Protocol Gateway for payload formats of XML and JSON only.

3. API-Connect v5/v5c APIs (which are implemented using MPGW).

Configuring WS-M at Domain Level

Enable the WS-M agent in each domain where payload of DataPower services should be captured (DataPower Gateway Web GUI → Web Services Management Agent):

Open

Configuring WS-M at Service Level

1. For Web Service Proxy, there is no need to change the service configuration.

2. For Multi-Protocol Gateways, follow the steps below:

   1. Enable the WS-M agent in the Multi-Protocol Gateway service configuration (DataPower Gateway Web GUI → select the service → Advanced tab):

      1. Turn on “Monitor via Web Services Management Agent”.

      2. Choose “All” in the “Message capture via Web Services Management Agent” filed.

      3. See the following screenshot:

         Open

         

   2. Since the WS-M agent captures only parsed XML and JSON payload, XML / JSON parsing should be enabled:

      1. Option 1: Change the “Request Type” and the “Response Type” to XML, JSON or SOAP.
         Note – If only one of the service direction (request or response) is configured with the supported payload formats, then only payload from that direction will be captured.
         See the following screenshot:

      2. Option 2: If you must configure the request and response type as “non-xml”, you can add a “transform” action to the processing policy that will cause payload parsing.
         In every processing rule, add a “Transform with processing control file” action.
         Choose the input=INPUT, output=NULL, “Input language”=XML or JSON (according to the service design).
         Note: Due to a DataPower Gateway limitation, the client request may not be captured in such a case.
         See the following screenshot: