Timeout for RFC Adapter

[#1]

Hello,

I have a HTTP --> RFC Synchronous scenario.

However I need to return timeout error in case RFC takes more than 30 secs as HTTP Response otherwise RFC Response will be sent as HTTP Response.

I tried using sync-async bridge in BPM and configured CHECK_FOR_ASYNC_RESPONSE_TIMEOUT = 30 sec.

I got a pipeline Timeout Error as a Response.

Can I catch this error as exception in BPM as I need to send Error Code for Timeout as Response in this case.

Or is there any other way I can set this timeout.

I dont want to apply this at Global level as for other interfaces it is 60 secs.

Is there any way to set the Timeout for particular interface?

Thanks in advance...

Thanks

Beena.

[Former Member]

Beena,

I think that you have missed my point. If you do not want to set alerts or parameters at a global level, or they do not meet this specific interface requirement, then you can use the control step to manage your requirement from within the BPM

For instance the timeout control step can throw an exception then the exception branch can send SMTP, HTTP response or whatever.

This will occur as long as the timeout is set to trigger before any relevant global timeout parameter. Then you exit the BPM cleanly before the global sync send parameter has timed out

FYI - an alert can be set up with conditions for specific party, service, interface etc

I hope that this has helped you,

Mike