cancel
Showing results for 
Search instead for 
Did you mean: 

Increase soap receiver timeout

former_member190239
Participant
0 Kudos

Hello Experts,

Currently we have all our sync scenarios timeout in 60 secs.

I have a new interface (proxy to SOAP) where the expected response time is going to be atleast 5 mins as it has a user action ..

can I change the time out fo ronly this interface?

note 856597 says parameter XI.Timeout and note 893713 says XMBWS.Timeout

which is the current one as we are currently on 7.4 dual stack

Accepted Solutions (1)

Accepted Solutions (1)

Liz_
Product and Topic Expert
Product and Topic Expert

Hi Ravi,

Please check the KBA with detailed screenshots:

1621719- Timeout parameters in SOAP Sender/Receiver Adapter

Best Regards,

Liz

Answers (4)

Answers (4)

dilipkkp2412
Contributor

Hi Ravi,

If service response depends on user action, your scenario should be configured in Asynchronous mode only.

However, about timeout, it can be at two level:

  1. At SAP-PI level
  2. At web-service hosted server level

To handle timeout in SAP-PI, you give a try, in soap receiver channel, set timeout using following details:

  • Module CallSapAdapter
  • Parameter syncTimeout (set value in milliseconds)
  • Channel screen:

Thanks & Regards,

Dilip

former_member192851
Active Participant
0 Kudos

Unsupported adapter type of ther receiver channel. Only File and JDBC receiver adapters can use CallSapAdapter module!

????????? ?????? *??, ???? ?? ?????? ?????? ????? ??? ??? ????????

former_member366655
Active Participant

Hi Ravi,

Yes you can do it Channel Specific. What is the Module you have used?

Regards,

Vivek Jain

dilipkkp2412
Contributor
0 Kudos

Dear Artem Solohin,

I don't know, if Ravi has already manged his timeout case. In his case, target service url too should support 5 mins timeout, only increasing it at receiver channel level will not help.

But, just for the info the CallSapAdapter module can be used in adapters like File/FTP, JDBC, JMS, HTTP_AAE, IDoc_AAE, SOAP etc.

Please have a look in below link for more info:

https://help.sap.com/viewer/5cf7d2de571a45cc81f91261668b7361/7.31.25/en-US/d98b5380972c403385c39295c...


Sorry for the delay in reply

Thanks & Regards,

Dilip Pandey

PRAGSMATIC
Participant
0 Kudos

You should definitely change the design pattern. Synchronous is not recommended in scenarious where User action confirms a transaction.