Skip to Content

REST Adapter Issue (REST vs REST Pooling)

Hi All,

First query I have what is difference between "REST and REST Pooling" ?

What is "incrementalToken" and in which situation we can used ?


Now coming to my requirement, when i tried to fetch token with Postman for XYZ API, my token looks like

I successfully fetched the test data from xyz api, by just passing the token in header and providing URL

But, when i tried to configure same thing in PO 7.40, it was throwing below error

"Error while processing inbound message. com.sap.engine.services.applocking.exception.AppLockingTechnicalLockException: The lifetime can not be the transaction, because currently no transaction is open.: The lifetime can not be the transaction, because currently no transaction is open"

I have posted this issue on scn and got response from SAP team member that it got resolved in note 2494100, this notes says to update the patch but updation of patch is very tedious work, it will take so much of time.

rest configuration you can see in below scn thread.

https://answers.sap.com/questions/303366/sap-po-rest-adapter-polling-exception-applockingte.html?childToView=12666450&answerPublished=true#answer-12666450

Now my question is

1. Since token_expiration value is 2019-04-24 11:41:02.000+0000, do i have to configure Incremental request, if yes then why because in postman directly i am able to make a call

2. Do we have any other solution than updating the patch ? Because it's so difficult, have to answer so many thing and it will take lot's more time.

3. I remember, i fetched the Ariba API data using sender REST Pooling by passing token in header, but don't know why here i need to update the patch ?

4. And please guide me with Incremental Request, i didn't understand it nicely, in which case we have to use it ?

for ex. for fetching test data from api my url is

https://<host_name>/groups

Appreciate your valuable time.

Regards,

Binod

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 06 at 03:08 AM

    First query I have what is difference between "REST and REST Pooling" ?

    Here is what I understood.

    REST is listening for on-demand request. REST Polling is actively checking sender source periodically.

    1. Since token_expiration value is 2019-04-24 11:41:02.000+0000, do i have to configure Incremental request, if yes then why because in postman directly i am able to make a call

    No, you don't have to. Just set suitable "Minimum Polling Interval (Seconds)" in the tab of "HTTP Reuqest" to comply with access token expiration interval

    2. Do we have any other solution than updating the patch ? Because it's so difficult, have to answer so many thing and it will take lot's more time.
    Haven't been this situation before. Sorry I cannot answer this.

    3. I remember, i fetched the Ariba API data using sender REST Pooling by passing token in header, but don't know why here i need to update the patch ?
    Is it because these 2 are different case where one is to fetch access token another is via access token to reach the data?

    4. And please guide me with Incremental Request, i didn't understand it nicely, in which case we have to use it ?
    Incremental Request is for the usage to fetch partial data piece by piece to combine entire data set when fetching the whole huge data set may possibly causing response time out or performance issue. You could either fetch your data by the dimension of timestamp, for example, getting "the day before yesterday" data, "yesterday" data, "today" data and so on

    or

    by paging the return data, if the REST api support this
    For more info, you could refer this link
    https://blogs.sap.com/2015/06/26/pi-rest-adapter-polling-a-rest-api/


    1.png (11.1 kB)
    Add comment
    10|10000 characters needed characters exceeded

    • Hi, Binod

      According to your description in the thread https://answers.sap.com/questions/724549/passing-dynamic-oauth-token-api-key-in-header-of-s.html. I personally think you could think out of the box and don't have to stick to the design that grasp token only on sender side.

      The scenario you described below could be fulfilled by SAP PO's bridge technique rather than accomplished in sender adapter. Then you could leverage UDF like others did.

      "Let me explain you the scenario :

      1. In 1st call we will get token

      2. in 2nd call with the help of token, it generates ChunkURI

      3. In 3rd call, have to make post call on ChunkURI along with passing the file"