on 12-23-2015 8:53 AM
Hi Midhun,
Is scenario synchronous? (since you wrote you fetch data from receiver system via RFC, I would assume, it is synchronous communication, by please confirm that). If so, by default Adapter Engine doesn't keep payload of synchronously processed messages. You can change this by change value of a property syncMessageRemover.removeBody (Java service XPI Service: Messaging System) to false. (for more details, see SAP Notes 1872758 and 1507698). Please note that even though it is technically feasible, it is not recommended for production environments - a reason for this is, synchronously processed messages are kept in memory of Adapter Engine, and keeping their payload will increase their memory footprint and may negatively affect entire memory consumption.
Depending on your logging needs, you may also get use of message logging functionality offered by Adapter Engine in releases 7.3 and higher, and described in SAP Note 1760915 and .
Regards,
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Vadim
I tried a REST synchronous scenario. I am able to read the message for that in Message Monitor.
When i try synchronous scenario from HTTP client, I am not able to see the payload.
I don't think it has to do with syncMessageRemover.
Both are synchronous scenarios only..
ideallyhttp client sends xml messages and it should be visible right
Midhun,
Did you check the ICO for both the scenarios? Does the REST Scenario has the Loggin/Staging enabled whereas your HTTP isn't?
Thx.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Justin
the configs were same in both ICOs and I found that strange.
I activated scenario specific and I got to se the message in Message monitor.
I am able to see the payload sent back by RFC in response flow
In request flow, I am not able to see the message. I downloaded it, it is downloaded as a .rar file and size zero..
wonder where the sender payload went
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.