on 01-27-2016 10:34 AM
Hi,
We currently have a problem with a Gateway service whilst transferring large amounts of data (>0.25GByte), intermittently during the transfer the transfer stops and eventually times-out, the performance-trace for a transfer looks identical for BOTH a successful/non-successful transfer.
When attempting to open the payload-trace, SAPGUI terminates and a short-dump is produced, thus no further information can be obtained.
There are no errors (-which we can find) on the Gateway when this problem occurs.
Has anyone experienced similar problems? Is it possible to complete a TCP/IP trace (– without causing further problems) on a production system?
I notice there is a parameter on the GW to test for network fragmentation (gw/nifragtest) on the network layer, could this help?
Any other suggestions?
thanks and regards,
Richard
Thank you to all for the suggestions, comments etc., it turns out that the problem with buffers lies in a different (non SAP) part of our system.
Thanks again,
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Richard,
According to me GW layer is not meant for transfer of large amount of data. Its for light weight application.
I feel SAP PI would be the suitable option here to handle huge data transfer.
Regards,
Ashwin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is some info that might be useful for you...
File size is mentioned in Internet Communication Manager level. Gateway does not restrict or impose anything.
Here is the link for you for further details ...
Still it would be worth considering if Gateway should be used as a medium to transfer very big files.
That is right. Gateway does not put any restrictions on size of the load.
Gateway puts OData restrictions on regular REST service. This 'OData' is suited/designed for consumption by UI libraries like SAPUI5. Seeing huge amount of data, I think you are doing a system to system communication, which is the main use case of SAP PI.
If you do not have SAP PI, I would suggest having a simple http ICF service for your requirement. That would save lots of parsing overhead (computation) and payload overhead (OData grammar).
Regards
Krishna
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.