The DataPower gateway’s Web Services Management (WS-M) payload capture is supported by IDG for the following servicesenables payload capture of DataPower services (WSP, MPGW) as well as API-Connect v5/v5c APIs.

The following services are supported:

1. Web Service Proxy starting firmware version 6.1.x .

2. Multi-Protocol Gateway starting firmware version 7.5.2.1 and DPOD version 1.0.2 for payload formats of XML and JSON .

In order for the IDG to capture payload via WS-M the following IDG configuration is needed:

1. Web Service Proxy – Can be fully configured via DPOD since only.

2. 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):

...

Configuring WS-M at Service Level

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

2. For Multi-Protocol Gateway – The following configuration needs to be done in the service configurationGateways, follow the steps below:

   1. Enable the WS-M agent

...

1. 1. in the Multi-Protocol Gateway service

...

1. 1. configuration (DataPower Gateway Web GUI → select the service → Advanced tab):

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

...

1. 1. 1. .

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

...

1. 1. 1. See the following screenshot:

         Image Added

   2. Since the WS-M agent

...

1. 1. captures only parsed XML and JSON

...

1. 1. 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.
         

...

1. 1. 1. See the following screenshot:

         Image Added

      2. Option

...

1. 1. 1. 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

...

1. 1. 1. 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).
         

...

1. 1. 1. Note: Due to

...

1. 1. 1. a DataPower Gateway limitation, the client request may not be captured

...

Web services management agent 

For each domain you would like to capture payload, you will need to manually enable the web services management agent (if it's disabled)

...

1. 1. 1. in such a case.
         See the following screenshot:

         Image Added