...
Symptoms
Some transactions are not showing WSM Payloads, even though WSM subscription was requested for them.
In /logs/wsmAgents/agent-flume_MonTier-WsmAgent-X.log (where X is the number of the wsm agent you use), you will see the following message(s):
12/07/2016 02:12:29,852- WARN o.m.a.f.h.NHttpFileServer [I/O-dispatch-3] wsmHttpSource1 -98b515b9-ed96-45dd-a999-248f6f19f1a3- Request ignored - With size 18615431 that limit 10485760
Overview
Each transaction payload contains 4 parts: Front-End request, Back-End request, Back-End response and Front-End response, the size of the payload equals to the size of all 4 parts.
The DataPower batches several transactions together before sending them to DPOD.
The default is grouping 20 transactions together.
DPOD WSM Agent sets a size limit for incoming requests, the default is 10MB, so DPOD will drop any requests that are larger than 10MB
Assuming you have a transaction with payload size of 1mb, and the DataPower grouped 20 of them before sending to DPOD, the total request size will be 20 x 1mb = 20mb , DPOD will drop this request and will not show the payloads.
Changing DPOD defaults
You can effect the number of transactions the DataPower will send to DPOD in each batch and the batch size.
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
wdp.wsm.push.max_envelope_siize