...
- Web Service Proxy starting firmware version 6.1.x .
- Multi-Protocol Gateway starting firmware version 7.5.2.1 and DPOD version 1.0.2 for payload formats XML and JSON.
...
- Enable the WS-M agent configuration in the Multi-Protocol Gateway service
- Enter the service -> advanced tab -> turn “Monitor via Web Services Management Agent” to “on”.
- Choose “All” in the “Message capture via Web Services Management Agent” filed.
...
- Enable XML / JSON parsing
The WS-M agent capture only parsed XML and JSON formats. In order for the service to parse the payload the following service configuration are needed.- Option one - 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.
- Option one - Change the “Request Type” and the “Response Type” to XML, JSON or SOAP.
...
- Option two – If you must configure the request and response type as “non-xml” you can add “transform” action to the processing policy that will cause payload parse.
- In every processing rule add “Transform with processing control file” action.
- Choose the input=INPUT, output=NULL, “Input language”=XML or JSON according to the service design.Notice –
- Option two – If you must configure the request and response type as “non-xml” you can add “transform” action to the processing policy that will cause payload parse.
| Info |
|---|
Due to IDG 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)
