Hi Dimitri
Unfortunately, that is the behavior of the Comm Channel Monitor that dates back to the days of RWB. The logs show the last 25 lines of entries related to a particular comm channel and therefore is intended to present just a "current snapshot" view of the channel at a point in time.
What is available in the logs is highly dependent on the nature of the selected comm channel:-
i) Sender channel acting in polling mode (i.e. SFTP, File)
Each polling interval will take at least a few lines of entries, you can normally only see entries related to about 4-6 polling intervals (regardless of whether there are messages produced during each interval). If the polling interval is very frequent, say 1 minute, then the logs shows only details for the last 4-6 minutes.
ii) Sender channel acting in listening mode (i.e. SOAP, RFC)
The logs shows entries each time a message is sent to the channel. Typically it has 3-4 entries for each message, so you can see entries related to the last 6-8 messages that was sent to the channel. If messages are sent frequently to this channel, then the logs are only for the past few minutes. Likewise, it is it a low volume interface, the logs might show messages for the past few days/weeks/months.
iii) Receiver channel
This is similar to (ii) above for messages sent by the Messaging System to the receiver channel.
If you want to see historical messages, Comm Channel Monitor is not the place to go. Use Message Monitor instead and filter by the iFlow related to the particular channel.
Rgds
Eng Swee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.