|
Home > Archive > BizTalk Server General > April 2006 > Enable routing for failed messages in BizTalk 2006
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 |
Enable routing for failed messages in BizTalk 2006
|
|
| stefanjohansson_2005@yahoo.se 2006-04-27, 7:26 am |
| I have created a solution that routes documents with errors separately
using the example here
http://www.biztalkgurus.com/Samples...ztalk-2006.html
And it works if the error occurs in the receive pipeline. For example
if the root tag is incorrect. But if I instead for example add a
Suspend shape in the Orchestration the message is suspended as usual.
How do I do to route all failed messages to the Orchestration that
handles them?
| |
| Doug Girard [MSFT] 2006-04-27, 7:26 am |
| Stefan,
I'm not sure I completely understand the question, but this feature allows
you to subscribe to messaging failures. Subscribers can be orchestrations
or send ports, for example. They can subscribe to specific failures (say
by failure code or by failure source), or they can generally subscribe to
all failures. If the latter is what you want, you might consider using a
filter on your orchestration such as: "ErrorReport.ErrorType Exists".
See "Using Failed Message Routing" in our documentation for more
information. An excerpt:
"An error message is a clone of the original failed message, with all
previously promoted properties demoted and with a set of error-specific
properties promoted to the message context. Previously promoted properties
are demoted to avoid unintended delivery to subscribers not designated to
receive the error message. The error message is published for distribution
to subscribers (orchestrations, send ports, and send port groups)."
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>From: stefanjohansson_2005@yahoo.se
>Newsgroups: microsoft.public.biztalk.general
>Subject: Enable routing for failed messages in BizTalk 2006
>Date: 24 Apr 2006 05:22:04 -0700
>Organization: http://groups.google.com
>Lines: 9
>Message-ID: <1145881324.392205.322640@t31g2000cwb.googlegroups.com>
>NNTP-Posting-Host: 193.41.32.254
>Mime-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1145881329 14819 127.0.0.1 (24 Apr 2006
12:22:09 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Mon, 24 Apr 2006 12:22:09 +0000 (UTC)
>User-Agent: G2/0.2
>X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1;
.NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1),gzip(gfe),gzip(gfe)
>Complaints-To: groups-abuse@google.com
>Injection-Info: t31g2000cwb.googlegroups.com; posting-host=193.41.32.254;
> posting- account=gPSdKw0AAAD1q0QO5bBxEloWnXlIVjam
>Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed.c
w.net!cw.net!news-FFM2.ecrc.de!news.glorb.com!postnews.google.com!t31g2000cw
b.googlegroups.com!not-for-mail
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:36893
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>I have created a solution that routes documents with errors separately
>using the example here
>http://www.biztalkgurus.com/Samples...g-Biztalk-2006.
html
>And it works if the error occurs in the receive pipeline. For example
>if the root tag is incorrect. But if I instead for example add a
>Suspend shape in the Orchestration the message is suspended as usual.
>How do I do to route all failed messages to the Orchestration that
>handles them?
>
>
| |
| stefanjohansson_2005@yahoo.se 2006-04-27, 7:26 am |
| Hi Doug
Thanks for your reply. Yes I could have given more details in my
question. I have enabled routing for failed messages in the receive and
send ports. I have an orchestration that subscribes to failed messages
with the filter ErrorReport.FailureCode Exists. If messages fails when
they are received or when they are written they are sent to the
orchestration that subscribes for suspended messages. But if the
message fails in the orchestration it is not sent to the orchestration
that subscribes for suspended messages. This seems logical considering
the configurations I have done. But I would like to know if there is a
way to have all suspended messages sent to the orchestration that
handles them.
| |
| Sam Vanhoutte 2006-04-27, 7:26 am |
| > Thanks for your reply. Yes I could have given more details in my
> question. I have enabled routing for failed messages in the receive and
> send ports. I have an orchestration that subscribes to failed messages
> with the filter ErrorReport.FailureCode Exists. If messages fails when
> they are received or when they are written they are sent to the
> orchestration that subscribes for suspended messages. But if the
> message fails in the orchestration it is not sent to the orchestration
> that subscribes for suspended messages. This seems logical considering
> the configurations I have done. But I would like to know if there is a
> way to have all suspended messages sent to the orchestration that
> handles them.
As Doug explained, this feature is implemented for messaging and not
orchestrations. In orchestrations you have more control over the process
flow, so you can easily write your custom exception handling and then route
the message of your choice through direct binding to the orchestration you
mentioned.
Best regards
| |
| Doug Girard [MSFT] 2006-04-27, 7:26 am |
| Right. Natively, this feature exists for messaging failures and
orchestration failures are probably better handled in orchestration
exception blocks. However, you can add these properties to any message's
context yourself and do a direct bind send to the Message Box if you're
really keen on one generic handling orchestration.
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>From: "Sam Vanhoutte" <firstname@companyname.be>
>References: <1145881324.392205.322640@t31g2000cwb.googlegroups.com>
<aDDVRt9ZGHA.5300@TK2MSFTNGXA01.phx.gbl>
<1145946913.193861.40280@i40g2000cwc.googlegroups.com>
>Subject: Re: Enable routing for failed messages in BizTalk 2006
>Date: Tue, 25 Apr 2006 10:35:49 +0200
>Lines: 21
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.2663
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OHMsFNEaGHA.1192@TK2MSFTNGP03.phx.gbl>
>Newsgroups: microsoft.public.biztalk.general
>NNTP-Posting-Host: dd57778aa.access.telenet.be 213.119.120.170
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:36938
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>
>As Doug explained, this feature is implemented for messaging and not
>orchestrations. In orchestrations you have more control over the process
>flow, so you can easily write your custom exception handling and then
route
>the message of your choice through direct binding to the orchestration you
>mentioned.
>
>Best regards
>
>
>
| |
| stefanjohansson_2005@yahoo.se 2006-04-27, 7:26 am |
| Ok it's a great new feature that I will have to test further. Thanks
for the answers.
|
|
|
|
|