|
Home > Archive > BizTalk Server Orchestration > June 2005 > Best practice to handle web service down in orchestration?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Best practice to handle web service down in orchestration?
|
|
| Eddie Tse 2005-05-21, 5:48 pm |
| Hi,
I would like to know if there is a best practice/recommendation for handling
error with web service consumed from orchestration? I know the SOAP send
port by default will retry 3 times at 5 minutes interval, but after that a
SOAP exception is reported back to orchestration.
Some people like to leave the retry logic in the send port and some say
handle it inside orchestration.
I am particularly interested in the scenerio where if the web service
BizTalk is calling is down, what pattern would work best such that the
orchestration will not end up as Suspended (Non resumable)
Thanks for any suggestion...
Ed
| |
| WenJun Zhang[msft] 2005-05-23, 7:50 am |
| Hi Eddie,
Catching SOAP exception within orchestration isn't difficult. Please
refer to the following blog:
Handling an Error in Orchestration with the SQL Adapter
http://dallas.sark.com/SarkBlog/mho.../10/22/442.aspx
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
| Scott Colestock 2005-05-23, 5:53 pm |
| Whether you choose to handle an exception in the orchestration or not
depends somewhat on the business scenario. Do you have other work you
should "undo" or "not do" if the web service call fails, for instance?
Avoiding suspended/non-resumable usually means that you will have a looping
construct in the orchestration that exits up on success, and retries while
things are failing (or until you give up.) It would be common to have a
"suspend" shape (in the failure path) so that an operations person has a
chance to remedy the situation, and can then resume the orchestrations via
HAT.
Scott Colestock
www.traceofthought.net
"Eddie Tse" <eddietse@online.nospam> wrote in message
news:eXVg$ggXFHA.3840@tk2msftngp13.phx.gbl...
> Hi,
>
> I would like to know if there is a best practice/recommendation for
> handling error with web service consumed from orchestration? I know the
> SOAP send port by default will retry 3 times at 5 minutes interval, but
> after that a SOAP exception is reported back to orchestration.
>
> Some people like to leave the retry logic in the send port and some say
> handle it inside orchestration.
>
> I am particularly interested in the scenerio where if the web service
> BizTalk is calling is down, what pattern would work best such that the
> orchestration will not end up as Suspended (Non resumable)
>
> Thanks for any suggestion...
>
>
> Ed
>
| |
| Eddie Tse 2005-06-09, 5:51 pm |
| Is it common to construct a dummy response message in the exception handler
part of a scope shape? If I try to use the response message after the scope
that calls a web service, the orchestration won't compile and it gives a
message not initialized error if I handled the exception and put in a
suspend shape.
"Scott Colestock" <scolestock@nospam_usa.net> wrote in message
news:uZVaEr5XFHA.3732@TK2MSFTNGP10.phx.gbl...
> Whether you choose to handle an exception in the orchestration or not
> depends somewhat on the business scenario. Do you have other work you
> should "undo" or "not do" if the web service call fails, for instance?
>
> Avoiding suspended/non-resumable usually means that you will have a
> looping construct in the orchestration that exits up on success, and
> retries while things are failing (or until you give up.) It would be
> common to have a "suspend" shape (in the failure path) so that an
> operations person has a chance to remedy the situation, and can then
> resume the orchestrations via HAT.
>
> Scott Colestock
> www.traceofthought.net
>
>
> "Eddie Tse" <eddietse@online.nospam> wrote in message
> news:eXVg$ggXFHA.3840@tk2msftngp13.phx.gbl...
>
>
| |
| Scott Colestock 2005-06-16, 5:50 pm |
| Can you describe a bit more how the orchestration is put together?
"Eddie Tse" <eddietse@online.nospam> wrote in message
news:eSz31iQbFHA.3444@TK2MSFTNGP10.phx.gbl...
> Is it common to construct a dummy response message in the exception
> handler part of a scope shape? If I try to use the response message after
> the scope that calls a web service, the orchestration won't compile and it
> gives a message not initialized error if I handled the exception and put
> in a suspend shape.
>
> "Scott Colestock" <scolestock@nospam_usa.net> wrote in message
> news:uZVaEr5XFHA.3732@TK2MSFTNGP10.phx.gbl...
>
>
|
|
|
|
|