on ‎2020 Dec 23 4:10 AM
Hi,
We have a APi call with request and response and policies / transformation. We are facing a issue due to the response size . We tried enabling streaming but it doesnt work since we have policies and transformation in place. Is there any alternative workaround or solution to handle this in API management . Kindly suggest.
{
"fault": {
"faultstring": "Body buffer overflow",
"detail": {
"errorcode": "protocol.http.TooBigBody"
}
}
}
Request clarification before answering.
Hi Amit,
Alternatively if you have SCPI (CPI) in your landscape you could implement pagination in SCPI also.
If its odata service or SOAP service which supports pagination you could use below blog for more details of implmentation.
Hope this helps !
thanks and regards,
Praveen T
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
SAP API Management has a 10 MB payload limit for synchronous API calls - which given the nature of API based integration is about the limit you would want to hit on API calls from an architectural perspective.
If you would like to work around this my recommendation would to implement a paging strategy within the API (e.g. the OData format allows for $top & $skip functionality natively in the API design to allow for pagination of large data).
If the API does not support pagination, or it is too much effort to implement pagination a second option is to combine SAP API management with SAP Open Connectors which can harmonize SAP and NonSAP APIs into a common format, and provide pagination natively as part of the response.
Regards,
Elijah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.