Skip to Content
author's profile photo Former Member
Former Member

Between RFC and Proxy which is better to handle Timeout

Hi Experts,

We have one HTTP to RFC synchronous scenario and we are currently getting time out error most of the time for that. The abap program is taking around 10 minutes to send response and in PI we are getting time out.

We discussed with ABAP team that they can not change the program logic. As the data volume is very high program will take that time.

To avoid the time out issue we are planning to change the set up to proxy. Please suggest whether proxy will be better than RFC or not and how to handle the time out.

We have already maintained : xiadapter.inbound.timeout.default to more than 3 minutes but it is not working.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Posted on Dec 30, 2014 at 06:08 PM

    Hi Swapnashree Nayak,

    Ten minutes is not a good performance for a synchronous scenario, even worse when the scenario is called constantly. May be you should wonder if it is better to have two async scenarios.

    With proxys scenarios you can increase the ICM timeout for example, but the problem can be in the ECC maximum runtime.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 30, 2014 at 03:57 PM

    It's good to go with Proxies when the data volume is high.

    However i don't think your parameter has some impact on your interface.

    What is your PI version? Did you try specifying the channel specific timeout and see if that helps?

    Setting a Channel-Specific Timeout - Advanced Adapter Engine - SAP Library

    For the CallSapAdapter and RfcAFBean modules, go to the Module tab page, enter the parameter namesyncTimeout and add a value in milliseconds.

    Add a comment
    10|10000 characters needed characters exceeded

    • Looks like you have manually added the callSAPadapter module to RFC adapter.

      callSAPadapter is not part of RFC adapter so I don't think it'll have any effect.

      However you don't need to add this module to use syncTimeout parameter. This parameter is supported by "RfcAFBean" modulebean too.

  • Posted on Dec 30, 2014 at 09:03 PM

    IMO, the change from RFC to proxy will not solve your timeout. Here you talk about processing time of more than 10 minutes. You might want to think about Http to file and file to proxy as two async scenarios and see whether that helps. Use AAE for both. Also, if the business rule allows then reduce the size of the message and split into few smaller parts...

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for your reply.. but issue is like, it is fedex website and when user is sending customer number as input in response he is expecting the result. So, we can not change it to Async .

      Is there any way to set any parameter at ECC side so that if it takes 10 minutes still we will not get time out at PI.

      If we change to proxy can we set any parameter in PI as well?

  • Posted on Dec 31, 2014 at 09:41 AM

    Hi Swapnashree,

    The processing time of 10 minutes is not a good performance. Try with the ABAP team to fine tune the code also you can do the table indexing so as to obtain the good performance.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.