on 01-15-2016 1:00 PM
Hi all,
I am doing a synchronous REST --- PI ---- ECC scenario. In the response message at times, PI is sending lots of records. I am delivering the response message as JSON. Since the output is huge, the client is asking for pagination in the output.
Does the REST communication channel support this?
If it is possible, which is best way to paginate? According to the records in response message or as per the html page length?
Regards
Harish
Hi Harish,
Pagination is not supported by a REST adapter: it transmits the whole response message (XML or JSON formatted) to a caller in a single transaction and session, in a single chunk. Thus, if a caller needs to receive smaller sets of data, they should:
Generally speaking, usage of synchronous communication mode for interfaces regularly generating and processing large messages, is not recommended, and shall be avoided and replaced with asynchronous mode whenever possible.
Regards,
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have a reverse situation with a REST Receiver channel and Proxy sender and the results fetched are paginated, with a next link ($skip token) for the next records to be fetched in sequence. Is there an easy way to fetch paginated results with the REST adapter, so that the proxy makes a single call but PI fetches all records in the result set?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Harish,
Why dont do you in ECC side,I mean proxy channel.
Get all the messages in PI ,for each record in REST trigger one proxy in SAP ECC.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
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.