...
Assuming you have a transaction with payload size of 1mb (300kb back-end and front-end requsets, and 200kb back-end and and front-end responses), and the DataPower grouped 20 of them before sending them to DPOD, the total request size will be 20 x 1mb = 20mb , DPOD will drop this request and will not show the payloads.
...
You can effect the number of transactions the DataPower will send to DPOD in each batch and the batch size - all the configuration is changes are done in DPOD and not in the DataPower.
...
edit /app/ui/MonTier-UI/conf/MonTierUI.conf
the relevant configuration keys are:
wdp.wsm.push.max_elements - how many transactions the DataPower will group together (the default is 20)
wdp.wsm.push.max_envelope_size -max batch size that the DataPower will send to DPOD (the default is 10485760)
Changing the max batch size DPOD can handle
| Note |
|---|
You will need to stop DPOD WSM agent from the CLI before changing the following values, and start it again afterwards. |
...
The relevant configuration key is:
MonTier-WsmAgent-1X.sources.wsmHttpSource1.requestSizeLimitInBytes - max batch size that DPOD will process (the default is 10485760)
Best Practices
It is better to lower the number of the batched payloads (wdp.wsm.push.max_elements) than to increase the batch size (wdp.wsm.push.max_envelope_size and wsmHttpSource1.requestSizeLimitInBytes) - making more smaller requests will allow both the DataPower and DPOD to work in parallel and will require less memory on both appliances. specifically, setting wsmHttpSource1.requestSizeLimitInBytes to a high value may put some stress on DataPower machines with a low amount of RAM.
If you still want to change the batch size because a specific transaction/batch of transaction is larger than 10mb, the best thing will be to raise the limit only for one specific WSM agent and choosing this agent when subscribing to WSM.
