This is something I keep on struggling with.
Splitting an XML message works fine but how to split a flat file ?
One of the approaches I took was using a flat file disassembler followed by
an XML disassembler in a receive pipeline. In the flat file disassembler, I
specified the envelope schema (which also contains the imported document
schema) somehow hoping that the flat file disassembler would take the
complete schema into account, while in the XML disassembler I specified both
(the envelope schema as envelope and the other schema as document).
The problem however is that the flat file disassembler doesn't seem to know
the root element of my document scheme ("the namespace:rootelement" element
is not declared" error message appears when trying to use the ffdasm
utility).
This somehow seems logical - after all, an envelope is an envelope - but
what is the solution then ?
Another approach I took was to use 3 schemas (the complete schema, the
envelope and the document - the complete schema being the combination of the
envelope and the document) but with this approach I ran into problems using
the same namespace twice.

Any help is highly appreciated.

Kristof

[ Post a follow-up to this message ]

Look at the following sample in the install directory which should give you
a good example:

<install
directory> \SDK\Samples\Pipelines\AssemblerDisassem
bler\EnvelopeProcessing

--------------------
| >>From: "Kristof Verschaetse" <kristof.verschaetse@belgacom.net>
| >>Newsgroups: microsoft.public.biztalk.general
| >>Subject: How to split a flat file using Document and Envelope Schemas
| >>Date: Tue, 22 Jun 2004 09:45:02 +0200
| >>X-Priority: 3
| >>X-MSMail-Priority: Normal
| >>X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
| >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
| >>Lines: 25
| >>Message-ID: <40d7e50b$0$8399$a0ced6e1@news.skynet.be>
| >>Organization: -= Belgacom Usenet Service =-
| >>NNTP-Posting-Host: 81.240.164.10
| >>X-Trace: 1087890699 newsread002.isp.belgacom.be 8399 81.240.164.10:2607
| >>X-Complaints-To: usenet-abuse@skynet.be
| >>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfeed.icl.net!proxad.net!
proxad.net!skynet.be!skynet.be!newspost001!tjb!not-for-mail
| >>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:16472
| >>X-Tomcat-NG: microsoft.public.biztalk.general
| >>
| >>This is something I keep on struggling with.
| >>Splitting an XML message works fine but how to split a flat file ?
| >>One of the approaches I took was using a flat file disassembler
followed by
| >>an XML disassembler in a receive pipeline. In the flat file
disassembler, I
| >>specified the envelope schema (which also contains the imported document
| >>schema) somehow hoping that the flat file disassembler would take the
| >>complete schema into account, while in the XML disassembler I specified
both
| >>(the envelope schema as envelope and the other schema as document).
| >>The problem however is that the flat file disassembler doesn't seem to
know
| >>the root element of my document scheme ("the namespace:rootelement"
element
| >>is not declared" error message appears when trying to use the ffdasm
| >>utility).
| >>This somehow seems logical - after all, an envelope is an envelope - but
| >>what is the solution then ?
| >>Another approach I took was to use 3 schemas (the complete schema, the
| >>envelope and the document - the complete schema being the combination
of the
| >>envelope and the document) but with this approach I ran into problems
using
| >>the same namespace twice.
| >>
| >>Any help is highly appreciated.
| >>
| >>Kristof
| >>
| >>
| >>
| >>

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]

Could you tell me how to split xml messages using XML disassembler. I have a
xml file Employees which I have to split into individual Employee messages.
I defined schema for Employees and Employee separately. Do I have to drive
this through any orchestration to split individual messages? There are
samples regarding flat file disassembler but there is no sample for XML
disassembler. Any help is appeciated.

Thanks,
Live_Love_Laugh

"Kristof Verschaetse" <kristof.verschaetse@belgacom.net> wrote in message
news:40d7e50b$0$8399$a0ced6e1@news.skynet.be...
> This is something I keep on struggling with.
> Splitting an XML message works fine but how to split a flat file ?
> One of the approaches I took was using a flat file disassembler followed
by
> an XML disassembler in a receive pipeline. In the flat file disassembler,
I
> specified the envelope schema (which also contains the imported document
> schema) somehow hoping that the flat file disassembler would take the
> complete schema into account, while in the XML disassembler I specified
both
> (the envelope schema as envelope and the other schema as document).
> The problem however is that the flat file disassembler doesn't seem to
know
> the root element of my document scheme ("the namespace:rootelement"
element
> is not declared" error message appears when trying to use the ffdasm
> utility).
> This somehow seems logical - after all, an envelope is an envelope - but
> what is the solution then ?
> Another approach I took was to use 3 schemas (the complete schema, the
> envelope and the document - the complete schema being the combination of
the
> envelope and the document) but with this approach I ran into problems
using
> the same namespace twice.
>
> Any help is highly appreciated.
>
> Kristof
>
>
>

[ Post a follow-up to this message ]

The example in the SDK directory that demonstrates how to split a flat file
can easily be modified to split an XML document.  Do the following:

Run the sample and save the output xml file for later use.
Modify your saved file to include multiple documents.
Add a new Receive Pipeline with an XML Disassembler with the envelope and
document specified.
Undeploy the SDK assembly.
Rebuild your project.
Deploy your updated project.
Modify the existing Receive Location EnvelopeProcessing_RL to use your new
Receive Pipeline (from above).
Change the Address of the Receive Location to have a file mask of *.* rather
than *.txt.
Drop the modified file from above into the EnvInput directory.
You should see the XML Document broken-up into individual documents.

For your reference here is a modified XML Message that contains 4 enveloped
documents:

<ns0:XmlEnvelope xmlns:ns0="http://EnvelopeProcessing.XmlEnvelope">
<ns0:Source>Northwind Shipping</ns0:Source>
<ns0:Document>
<purchaseOrder orderDate="1999-10-20"
xmlns="http://EnvelopeProcessing.PO">
<shipTo country="US" xmlns="">
<name>Alice Smith</name>
<street>123 Maple Street</street>
<city>Mill Valley</city>
<state>CA</state>
<zip>90952</zip>
</shipTo>
<billTo country="US" xmlns="">
<name>Robert Smith</name>
<street>8 Oak Avenue</street>
<city>Old Town</city>
<state>PA</state>
<zip>95819</zip>
</billTo>
<comment>Hurry, my lawn is going wild!</comment>
<items xmlns="">
<item partNum="872-AA">
<productName>Lawnmower</productName>
<quantity>1</quantity>
<USPrice>148.95</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
</item>
<item partNum="926-AA">
<productName>Baby Monitor</productName>
<quantity>1</quantity>
<USPrice>39.98</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
<shipDate>1999-10-21</shipDate>
</item>
</items>
</purchaseOrder>
</ns0:Document>
<ns0:Document>
<purchaseOrder orderDate="1999-10-20"
xmlns="http://EnvelopeProcessing.PO">
<shipTo country="US" xmlns="">
<name>Alice Smith</name>
<street>123 Maple Street</street>
<city>Mill Valley</city>
<state>CA</state>
<zip>90952</zip>
</shipTo>
<billTo country="US" xmlns="">
<name>Robert Smith</name>
<street>8 Oak Avenue</street>
<city>Old Town</city>
<state>PA</state>
<zip>95819</zip>
</billTo>
<comment>Hurry, my lawn is going wild!</comment>
<items xmlns="">
<item partNum="872-AA">
<productName>Lawnmower</productName>
<quantity>1</quantity>
<USPrice>148.95</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
</item>
<item partNum="926-AA">
<productName>Baby Monitor</productName>
<quantity>1</quantity>
<USPrice>39.98</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
<shipDate>1999-10-21</shipDate>
</item>
</items>
</purchaseOrder>
</ns0:Document>
<ns0:Document>
<purchaseOrder orderDate="1999-10-20"
xmlns="http://EnvelopeProcessing.PO">
<shipTo country="US" xmlns="">
<name>Alice Smith</name>
<street>123 Maple Street</street>
<city>Mill Valley</city>
<state>CA</state>
<zip>90952</zip>
</shipTo>
<billTo country="US" xmlns="">
<name>Robert Smith</name>
<street>8 Oak Avenue</street>
<city>Old Town</city>
<state>PA</state>
<zip>95819</zip>
</billTo>
<comment>Hurry, my lawn is going wild!</comment>
<items xmlns="">
<item partNum="872-AA">
<productName>Lawnmower</productName>
<quantity>1</quantity>
<USPrice>148.95</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
</item>
<item partNum="926-AA">
<productName>Baby Monitor</productName>
<quantity>1</quantity>
<USPrice>39.98</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
<shipDate>1999-10-21</shipDate>
</item>
</items>
</purchaseOrder>
</ns0:Document>
<ns0:Document>
<purchaseOrder orderDate="1999-10-20"
xmlns="http://EnvelopeProcessing.PO">
<shipTo country="US" xmlns="">
<name>Alice Smith</name>
<street>123 Maple Street</street>
<city>Mill Valley</city>
<state>CA</state>
<zip>90952</zip>
</shipTo>
<billTo country="US" xmlns="">
<name>Robert Smith</name>
<street>8 Oak Avenue</street>
<city>Old Town</city>
<state>PA</state>
<zip>95819</zip>
</billTo>
<comment>Hurry, my lawn is going wild!</comment>
<items xmlns="">
<item partNum="872-AA">
<productName>Lawnmower</productName>
<quantity>1</quantity>
<USPrice>148.95</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
</item>
<item partNum="926-AA">
<productName>Baby Monitor</productName>
<quantity>1</quantity>
<USPrice>39.98</USPrice>
<comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
electric</comment>
<shipDate>1999-10-21</shipDate>
</item>
</items>
</purchaseOrder>
</ns0:Document>
</ns0:XmlEnvelope>

--
Dave

This posting is provided "AS IS" with no warranties, and confers no rights.

"Live_Love_Laugh" <OnlineSubscribe@yahoo.com> wrote in message
news:eEY1XZGYEHA.4092@TK2MSFTNGP11.phx.gbl...
> Could you tell me how to split xml messages using XML disassembler. I have
a
> xml file Employees which I have to split into individual Employee
messages.
> I defined schema for Employees and Employee separately. Do I have to drive
> this through any orchestration to split individual messages? There are
> samples regarding flat file disassembler but there is no sample for XML
> disassembler. Any help is appeciated.
>
> Thanks,
> Live_Love_Laugh
>
> "Kristof Verschaetse" <kristof.verschaetse@belgacom.net> wrote in message
> news:40d7e50b$0$8399$a0ced6e1@news.skynet.be... 
> by 
disassembler,[vbcol=seagreen]
> I 
> both 
> know 
> element 
> the 
> using 
>
>

[ Post a follow-up to this message ]

Thanks for the help. I tried implementing that. But I am getting error
"Error in accessing the part data or one of its fragments. The part or
fragment may not exist in database" while testing the orchestration. This
information I got it from suspended orchestration service details.

Any ideas?

Thanks,
Live_Love_Laugh

"David Downing [MSFT]" <ddowning@online.microsoft.com> wrote in message
news:%23o2kkzGYEHA.1152@TK2MSFTNGP09.phx.gbl...
> The example in the SDK directory that demonstrates how to split a flat
file
> can easily be modified to split an XML document.  Do the following:
>
> Run the sample and save the output xml file for later use.
> Modify your saved file to include multiple documents.
> Add a new Receive Pipeline with an XML Disassembler with the envelope and
> document specified.
> Undeploy the SDK assembly.
> Rebuild your project.
> Deploy your updated project.
> Modify the existing Receive Location EnvelopeProcessing_RL to use your new
> Receive Pipeline (from above).
> Change the Address of the Receive Location to have a file mask of *.*
rather
> than *.txt.
> Drop the modified file from above into the EnvInput directory.
> You should see the XML Document broken-up into individual documents.
>
> For your reference here is a modified XML Message that contains 4
enveloped
> documents:
>
> <ns0:XmlEnvelope xmlns:ns0="http://EnvelopeProcessing.XmlEnvelope">
>  <ns0:Source>Northwind Shipping</ns0:Source>
>  <ns0:Document>
>   <purchaseOrder orderDate="1999-10-20"
> xmlns="http://EnvelopeProcessing.PO">
>    <shipTo country="US" xmlns="">
>     <name>Alice Smith</name>
>     <street>123 Maple Street</street>
>     <city>Mill Valley</city>
>     <state>CA</state>
>     <zip>90952</zip>
>    </shipTo>
>    <billTo country="US" xmlns="">
>     <name>Robert Smith</name>
>     <street>8 Oak Avenue</street>
>     <city>Old Town</city>
>     <state>PA</state>
>     <zip>95819</zip>
>    </billTo>
>    <comment>Hurry, my lawn is going wild!</comment>
>    <items xmlns="">
>     <item partNum="872-AA">
>      <productName>Lawnmower</productName>
>      <quantity>1</quantity>
>      <USPrice>148.95</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>     </item>
>     <item partNum="926-AA">
>      <productName>Baby Monitor</productName>
>      <quantity>1</quantity>
>      <USPrice>39.98</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>      <shipDate>1999-10-21</shipDate>
>     </item>
>    </items>
>   </purchaseOrder>
>  </ns0:Document>
>  <ns0:Document>
>   <purchaseOrder orderDate="1999-10-20"
> xmlns="http://EnvelopeProcessing.PO">
>    <shipTo country="US" xmlns="">
>     <name>Alice Smith</name>
>     <street>123 Maple Street</street>
>     <city>Mill Valley</city>
>     <state>CA</state>
>     <zip>90952</zip>
>    </shipTo>
>    <billTo country="US" xmlns="">
>     <name>Robert Smith</name>
>     <street>8 Oak Avenue</street>
>     <city>Old Town</city>
>     <state>PA</state>
>     <zip>95819</zip>
>    </billTo>
>    <comment>Hurry, my lawn is going wild!</comment>
>    <items xmlns="">
>     <item partNum="872-AA">
>      <productName>Lawnmower</productName>
>      <quantity>1</quantity>
>      <USPrice>148.95</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>     </item>
>     <item partNum="926-AA">
>      <productName>Baby Monitor</productName>
>      <quantity>1</quantity>
>      <USPrice>39.98</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>      <shipDate>1999-10-21</shipDate>
>     </item>
>    </items>
>   </purchaseOrder>
>  </ns0:Document>
>  <ns0:Document>
>   <purchaseOrder orderDate="1999-10-20"
> xmlns="http://EnvelopeProcessing.PO">
>    <shipTo country="US" xmlns="">
>     <name>Alice Smith</name>
>     <street>123 Maple Street</street>
>     <city>Mill Valley</city>
>     <state>CA</state>
>     <zip>90952</zip>
>    </shipTo>
>    <billTo country="US" xmlns="">
>     <name>Robert Smith</name>
>     <street>8 Oak Avenue</street>
>     <city>Old Town</city>
>     <state>PA</state>
>     <zip>95819</zip>
>    </billTo>
>    <comment>Hurry, my lawn is going wild!</comment>
>    <items xmlns="">
>     <item partNum="872-AA">
>      <productName>Lawnmower</productName>
>      <quantity>1</quantity>
>      <USPrice>148.95</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>     </item>
>     <item partNum="926-AA">
>      <productName>Baby Monitor</productName>
>      <quantity>1</quantity>
>      <USPrice>39.98</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>      <shipDate>1999-10-21</shipDate>
>     </item>
>    </items>
>   </purchaseOrder>
>  </ns0:Document>
>  <ns0:Document>
>   <purchaseOrder orderDate="1999-10-20"
> xmlns="http://EnvelopeProcessing.PO">
>    <shipTo country="US" xmlns="">
>     <name>Alice Smith</name>
>     <street>123 Maple Street</street>
>     <city>Mill Valley</city>
>     <state>CA</state>
>     <zip>90952</zip>
>    </shipTo>
>    <billTo country="US" xmlns="">
>     <name>Robert Smith</name>
>     <street>8 Oak Avenue</street>
>     <city>Old Town</city>
>     <state>PA</state>
>     <zip>95819</zip>
>    </billTo>
>    <comment>Hurry, my lawn is going wild!</comment>
>    <items xmlns="">
>     <item partNum="872-AA">
>      <productName>Lawnmower</productName>
>      <quantity>1</quantity>
>      <USPrice>148.95</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>     </item>
>     <item partNum="926-AA">
>      <productName>Baby Monitor</productName>
>      <quantity>1</quantity>
>      <USPrice>39.98</USPrice>
>      <comment xmlns="http://EnvelopeProcessing.PO">Confirm this is
> electric</comment>
>      <shipDate>1999-10-21</shipDate>
>     </item>
>    </items>
>   </purchaseOrder>
>  </ns0:Document>
> </ns0:XmlEnvelope>
>
> --
> Dave
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Live_Love_Laugh" <OnlineSubscribe@yahoo.com> wrote in message
> news:eEY1XZGYEHA.4092@TK2MSFTNGP11.phx.gbl... 
have[vbcol=seagreen]
> a 
> messages. 
drive[vbcol=seagreen] 
message[vbcol=seagreen] 
followed[vbcol=seagreen] 
> disassembler, 
document[vbcol=seagreen] 
specified[vbcol=seagreen] 
but[vbcol=seagreen] 
of[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

I have to appologize for not being an orchestration expert, but I wanted to
provide you with a messaging solution you can use as a reference.  I
modified the EnvelopeProcessing sample and changed it to use XML rather than
flat file.  You should be able to run setup.bat to install the sample (make
sure you run cleanup on the existing EnvelopeProcessing sample first).
After you've successfully installed the attached sample, copy the file from
.\data\TestData.xml into .\EnvInput\   You should see three XML documents
placed into the .\EnvOutput.

Dave
--------------------[vbcol=seagreen] 
you[vbcol=seagreen] 
81.240.164.10:2607[vbcol=seagreen] 
08[vbcol=seagreen] 
t![vbcol=seagreen] 
document[vbcol=seagreen] 
specified[vbcol=seagreen] 
to[vbcol=seagreen] 
but[vbcol=seagreen] 
rights.[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]

I tried using Envelopes based on similar set of instructions. But I am
getting the error in the receive pipeline:
Reason: The disassembler cannot retrieve the document specification by using
this type: "TRPropertyInformation". Either the schema is not deployed
correctly, or more than one schema is deployed for the same message type.

From the health and activity monitoring tool, the error for this suspended
activity is "error in accessing the part data or one of its fragments. The
part or fragment may not exist in the database" in event log.

Any ideas?

Thanks,
Live_Love_Laugh

""David Downing [MSFT]"" <ddowning@online.microsoft.com> wrote in messag
e
news:ylE3JJ4YEHA.2804@cpmsftngxa06.phx.gbl...
> I have to appologize for not being an orchestration expert, but I wanted
to
> provide you with a messaging solution you can use as a reference.  I
> modified the EnvelopeProcessing sample and changed it to use XML rather
than
> flat file.  You should be able to run setup.bat to install the sample
(make
> sure you run cleanup on the existing EnvelopeProcessing sample first).
> After you've successfully installed the attached sample, copy the file
from
> \data\TestData.xml into .\EnvInput\   You should see three XML documents
> placed into the .\EnvOutput.
>
> Dave
> -------------------- 
Schemas[vbcol=seagreen] 
> you 
> 
Schemas[vbcol=seagreen] 
> 81.240.164.10:2607 
> 
> 08
> 
> t! 
> document 
the[vbcol=seagreen] 
> specified 
> to 
> but 
the[vbcol=seagreen] 
combination[vbcol=seagreen] 
problems[vbcol=seagreen] 
> rights. 
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> EBusiness Server Team

[ Post a follow-up to this message ]

Looks like you still had the previous project deployed.  Because the sample
project and the one I sent used the same schemas, you're probably running
into a conflict.  The first thing I'd try is opening Visual Studio and run
View | BizTalk Explorer.  Click on the refresh button.  Expand the tree for
your server database.  Look at the assemblies that are deployed.  If you
see more than one that might have the sample schemas in it, right-click on
each of the assemblies and click undeploy.  Make sure all of them get
undeployed.

Stop and Restart the BizTalk Service to make sure any schemas that are
cached are cleaned up.
Open a command window.
Go to the directory where the updated project is.
Run setup.bat.
Copy data\TestData.xml into .\EnvInput\

You should see three XML documents placed into the .\EnvOutput.

Hope that helps...
Dave

--------------------[vbcol=seagreen] 
<GkbUWWkWEHA.1996@cpmsftngxa10.phx.gbl>
<ylE3JJ4YEHA.2804@cpmsftngxa06.phx.gbl>[vbcol=seagreen] 
cpmsftngxa06.phx.gbl!TK2MSFTNGXS01.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
8.phx.gbl!tk2msftngp13.phx.gbl[vbcol=seagreen] 
using[vbcol=seagreen] 
give[vbcol=seagreen] 
g[vbcol=seagreen] 
GP[vbcol=seagreen] 
ne[vbcol=seagreen] 
document).[vbcol=seagreen] 
seem[vbcol=seagreen] 
namespace:rootelement"[vbcol=seagreen] 
ffdasm[vbcol=seagreen] 
envelope -[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]