|
Home > Archive > BizTalk Server General > April 2006 > Recoverable interchange processing in 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 |
Recoverable interchange processing in 2006
|
|
|
| I have read a little about this and it seems good idea.
What sort of things can it do?
| |
| Tomas Restrepo \(MVP\) 2006-04-10, 7:33 pm |
| Ben,
>I have read a little about this and it seems good idea.
> What sort of things can it do?
You should take a look at
http://www.microsoft.com/biztalk/te...rs/runtime.mspx
where the feature is explained.
Basically this is an option that is relevant when you are doing debatching
in receive pipelines using either the Xml or Flat File disassembler to avoid
having an error in one of the individual messages generated to suspend the
entire interchange.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
|
| In the example it talks about successfully parsed and validated. What are
the individual messages validated against? Thank you.
"Tomas Restrepo (MVP)" wrote:
> Ben,
>
>
> You should take a look at
> http://www.microsoft.com/biztalk/te...rs/runtime.mspx
> where the feature is explained.
>
> Basically this is an option that is relevant when you are doing debatching
> in receive pipelines using either the Xml or Flat File disassembler to avoid
> having an error in one of the individual messages generated to suspend the
> entire interchange.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Tomas Restrepo \(MVP\) 2006-04-10, 7:33 pm |
| Ben,
> In the example it talks about successfully parsed and validated. What are
> the individual messages validated against? Thank you.
The individual schema. Remember that when debatching XML messages, you
create at least 2 schemas: the envelope schema and the individual message
schema (though this could be more than one).
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
|
| The recoverable interchange example it is a flat file. In a flat file
dissasembler there is not an option to specify an envelope schema. So how
would this work?
Thank you.
"Tomas Restrepo (MVP)" wrote:
> Ben,
>
>
> The individual schema. Remember that when debatching XML messages, you
> create at least 2 schemas: the envelope schema and the individual message
> schema (though this could be more than one).
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Tomas Restrepo \(MVP\) 2006-04-10, 7:33 pm |
| BenW,
> The recoverable interchange example it is a flat file. In a flat file
> dissasembler there is not an option to specify an envelope schema. So how
> would this work?
In a flat file case, you specify a body document schema, and optionally a
header and/or footer schema. However, the same basic rule applies that
multiple records can be broken up from the body of the message based on the
document schema.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
|
| On a Flat flat file disassembler there is a property 'Validate document
structure'. What is validated if the disassember 'Document schema' property
is set to the schema that defines the flat file received?
Thank you.
"Tomas Restrepo (MVP)" wrote:
> BenW,
>
>
> In a flat file case, you specify a body document schema, and optionally a
> header and/or footer schema. However, the same basic rule applies that
> multiple records can be broken up from the body of the message based on the
> document schema.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Doug Girard [MSFT] 2006-04-10, 7:34 pm |
| Just keep in mind that this feature is subject to some conditions. There
are certain situations when processing XML or FF files using this feature
which will not allow for recovery, such as mal-formed XML. Note that it is
easier for the disassembler to recover from XML document failures and find
the next record within the interchange to begin processing again than to do
the same with flat files. I believe failures encountered within a flat
file document cause the DASM to commit the records already processed, but
abandon the remaining records of the interchange yet to be processed, but
consult the BizTalk documentation for complete information about this new
feature.
Regards,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>From: "Tomas Restrepo \(MVP\)" <tomasr@mvps.org>
>References: <AE00C223-3466-448A-AEE9-9068B49BCEC1@microsoft.com>
<#CySrOyVGHA.3760@TK2MSFTNGP15.phx.gbl>
<3DB5D21B-0E56-4D9B-9AA6-7D1AF4F2FB51@microsoft.com>
<uhouyJ$VGHA.1160@TK2MSFTNGP09.phx.gbl>
<2F7804E0-8F39-434D-A5E1-DDFDEA2890CE@microsoft.com>
>Subject: Re: Recoverable interchange processing in 2006
>Date: Wed, 5 Apr 2006 08:10:29 -0500
>Lines: 18
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>X-RFC2646: Format=Flowed; Original
>Message-ID: <uWrsRJLWGHA.1348@TK2MSFTNGP05.phx.gbl>
>Newsgroups: microsoft.public.biztalk.general
>NNTP-Posting-Host: cable200-116-11-185.epm.net.co 200.116.11.185
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:36350
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>BenW,
>
how[vbcol=seagreen]
>
>In a flat file case, you specify a body document schema, and optionally a
>header and/or footer schema. However, the same basic rule applies that
>multiple records can be broken up from the body of the message based on
the
>document schema.
>
>
>--
>Tomas Restrepo
>tomasr@mvps.org
>http://www.winterdom.com/
>
>
>
| |
| Stephen W. Thomas 2006-04-18, 12:46 am |
| Ben,
If you are still looking for more information on Recoverable Interchange
Processing, I have a short video here:
http://www.biztalkgurus.com/Video/R...2006-Video.html
You can also download the sample code covered in the video.
It’s based on a non-RTM version of BizTalk 2006, but the concepts should be
the same.
Stephen W. Thomas
http://www.biztalkgurus.com
"BenW" wrote:
[vbcol=seagreen]
> On a Flat flat file disassembler there is a property 'Validate document
> structure'. What is validated if the disassember 'Document schema' property
> is set to the schema that defines the flat file received?
>
> Thank you.
>
> "Tomas Restrepo (MVP)" wrote:
>
| |
|
| Thanks Doug.
If what you say is correct then recoverable interchange does not work
correctly for flat files.
The online documentation in, Example 2 Interchange Processing, describes
how, when file is successfully parsed, a failed message is placed in the
Suspended queue and the successful messages propagate through the pipeline
ready to be published. The original interchange is then discarded.
The white paper has a similar this example for a flat file with recoverable
interchange.
Can this be confirmed as this is one of the significant new features of
BizTalk 2006.
Thank you.
BenW
"Doug Girard [MSFT]" wrote:
> Just keep in mind that this feature is subject to some conditions. There
> are certain situations when processing XML or FF files using this feature
> which will not allow for recovery, such as mal-formed XML. Note that it is
> easier for the disassembler to recover from XML document failures and find
> the next record within the interchange to begin processing again than to do
> the same with flat files. I believe failures encountered within a flat
> file document cause the DASM to commit the records already processed, but
> abandon the remaining records of the interchange yet to be processed, but
> consult the BizTalk documentation for complete information about this new
> feature.
>
> Regards,
> Doug Girard [MSFT]
>
> Note: This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --------------------
> <#CySrOyVGHA.3760@TK2MSFTNGP15.phx.gbl>
> <3DB5D21B-0E56-4D9B-9AA6-7D1AF4F2FB51@microsoft.com>
> <uhouyJ$VGHA.1160@TK2MSFTNGP09.phx.gbl>
> <2F7804E0-8F39-434D-A5E1-DDFDEA2890CE@microsoft.com>
> how
> the
>
>
| |
| Doug Girard [MSFT] 2006-04-28, 1:14 pm |
| Some clarification...
The flat file disassembler does support recoverable interchange processing
and works best if documents have tag identifiers. When using tag
identifiers, all bad "sub-documents" will be suspended as individual
messages. All successfully parsed "sub-documents" will be submitted to the
Message Box.
However, if documents do not have tag identifiers, then the disassembler
cannot reliably determine the next appropriate resume point, so it suspends
all the "sub-documents" starting from the failed one as one message. All
"sub-documents" before the failed one are successfully submitted to the
Message Box individually for further processing.
This is all by design.
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: Recoverable interchange processing in 2006
>thread-index: AcZkyG1mX3rC22oQSX6iZVnRvgn1kA==
>X-WBNR-Posting-Host: 81.151.254.104
>From: =?Utf-8?B?QmVuVw==?= <BenW@discussions.microsoft.com>
>References: <AE00C223-3466-448A-AEE9-9068B49BCEC1@microsoft.com>
<#CySrOyVGHA.3760@TK2MSFTNGP15.phx.gbl>
<3DB5D21B-0E56-4D9B-9AA6-7D1AF4F2FB51@microsoft.com>
<uhouyJ$VGHA.1160@TK2MSFTNGP09.phx.gbl>
<2F7804E0-8F39-434D-A5E1-DDFDEA2890CE@microsoft.com>
<uWrsRJLWGHA.1348@TK2MSFTNGP05.phx.gbl>
<GLzbyqPWGHA.5296@TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Recoverable interchange processing in 2006
>Date: Thu, 20 Apr 2006 15:19:01 -0700
>Lines: 84
>Message-ID: <5D92FF0D-97D4-4F22-B440-BBF527AAF7C2@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.biztalk.general
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:36843
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>Thanks Doug.
>
>If what you say is correct then recoverable interchange does not work
>correctly for flat files.
>
>The online documentation in, Example 2 Interchange Processing, describes
>how, when file is successfully parsed, a failed message is placed in the
>Suspended queue and the successful messages propagate through the pipeline
>ready to be published. The original interchange is then discarded.
>
>The white paper has a similar this example for a flat file with
recoverable
>interchange.
>
>Can this be confirmed as this is one of the significant new features of
>BizTalk 2006.
>
>Thank you.
>
>BenW
>
>
>"Doug Girard [MSFT]" wrote:
>
There[vbcol=seagreen]
feature[vbcol=seagreen]
is[vbcol=seagreen]
find[vbcol=seagreen]
do[vbcol=seagreen]
but[vbcol=seagreen]
but[vbcol=seagreen]
new[vbcol=seagreen]
no[vbcol=seagreen]
So[vbcol=seagreen]
a[vbcol=seagreen]
>
|
|
|
|
|