Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Envelope Schema issue
- This topic has 0 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
February 5, 2007 at 11:16 AM #17567
I can't add an attachement, so to see the screen shots of my issue, I also posted this on microsoft.public.biztalk.general and that is where you can get the word document.
NOTE: I've gotten some feedback saying I can't have "element" nodes in my input document and that I should create a custom disassembler for my XML document and "transform" them to "attribute" nodes and then I would be OK… I don't know how to do that so if anyone could point me in the right direction, I would appreciate it. I know how to (and already have) created the custom pipeline, I just don't know how to transform from "element" to "attribute". Also, I have 10's of thousands "documents" in my input file, so this is already a performance hog, so I need to keep performance in mind. I really don't need the elements that are in the input document that are casuing my issue, so if there is a quick way to just remove them that would be great! This will make a lot more sense if you could see my word document, so if you would like me to email it to you, please respond to this post and I would be happy to!
Project background
1) I am using BTS 2006
2) I am receiving a large XML file that contains data that I need to parse
through and create separate output XML files that have nearly the exact
layout as the input XML file.
3) I have a pipeline that disassembles the input file
4) My orchestration takes 1 record at a time, massages the data, determines
which output file the record needs to be appended to, and other misc stuff
is done in the orchestration.Here is where my issue starts
(my word document has screen shots and detail)
1) I create envelope and document schemas for the input XML file… There is
one "root" node called "Billing11", and 3 element fields under the root
node, then the "document" follows (and this can have unlimited number of
recs), then after ALL the document records, there is a final element field.
2) If I remove the 3 element nodes and the final element node in the input
file and the schema definition, I can get my project to process the
envelope/document to process just fine.
3) The problem is that in production, those nodes need to be there and they
need to be placed in the same format in the output XML file
4) When I test with the nodes in, I get an error basically saying "The
CARRIER node is invalid".So my question is how do I process this type of XML document, and how do I
create the output document… how do I set up the input and output envelope
and document schema definitions?This is the content of my word document WITHOUT the screen shots…
1) This is what the input schema looks like before I split it out into an envelope schema and document schema…
]
The “BR” node in my document that is repeated MANY times in the file I am receiving as input.
2) I created the envelope schema without the CARRIER, DID, GMT, and CT nodes because that is where I am having my issue… If I remove those 4 nodes from the actual file I process, and I don’t have them in my schema definition, I process my file just fine.
Properties for the any node
3) I created a ‘document’ schema for the BR node and here it is, nothing fancy!
4) I’m trying to take baby steps, so I am just adding in the CARRIER node to the Envelope schema. Here is what it looks like (see next image below)… I set the BILLING11 node’s Body Xpath property to this… /*[local-name()='BILLING11' and namespace-uri()=''] I promoted the CARRIER node to a distinguished field because I need that value when I am processing each BR record in my Orchestration. ( I am trying to follow this article… http://blogs.msdn.com/richardbpi/archive/2006/05/08/592476.aspx )
5) Here is what my document schema looks like… I first tried to put the CARRIER node directly under the BR node (like the article above says to do), but I get an error in the disassembler pipeline saying it expects the CARRIER node to be the first node in the BR record (which obviously it is not, in the physical input file… I was just trying to follow the article)… I then moved it outside of the BR node, then I get this error “The 'CARRIER' element is not declared.”.
6) here is some information on my input files (schemas).
I'm using BizTalk 2006 and I am receiving an XML file that I need to create an envelope schema and a document schema for.
I can get the envelope processing to work just fine with a modified version of the schema (I remove the red nodes), but the actual schema has 3 additional nodes under the "root" node(<BILLING11>) and 1 additional node at the end of the "<br>" records.
The purple node "<BILLING11>" is the root
The black nodes "<br>" are the actual records
The red nodes "<CARRIER>, <DID>, <GMT>, and <CT> " are the additional nodes that I don't know what to do with.
THIS schema I can get to work
<BILLING11>
<br>
<EI>1197459579</EI>
<CID>64</CID>
<ADS>3600</ADS>
<SID>311416418703137</SID>
<NSID/>
<PID>8071</PID>
<PN>QC00080805</PN>
<NM>RingTone JukeBox 2</NM>
<AN>RingTone JukeBox 2</AN>
<MF>9 Squared</MF>
<SN/>
<RF>N</RF>
<LTS>01092007 034638</LTS>
<GMT>01092007 094638</GMT>
<TY>DL</TY>
<PM>1</PM>
<PB>3</PB>
<PV>1</PV>
<PR>+.00</PR>
<CY>1</CY>
<DP>+.00</DP>
<DCY>1</DCY>
<AR/>
<AD/>
<AP/>
<AE/>
<AI/>
<ADT>P</ADT>
<TF>N</TF>
<NF>Y</NF>
<PP/>
<EX>0</EX>
<GPS>N</GPS>
<HWID>79E29862D284E292E4F9A79541636F69</HWID>
<BF>N</BF>
<ATY/>
<WA>Y</WA>
<CDATE>01092007 095107</CDATE>
<CREATOR>SystemManager</CREATOR>
</BR>
<br>
<EI>1197459577</EI>
<CID>64</CID>
<ADS>3600</ADS>
<SID>310005074502771</SID>
<NSID/>
<PID>8071</PID>
<PN>QC00061447</PN>
<NM>FlixTones</NM>
<AN>FlixTones</AN>
<MF>9 Squared</MF>
<SN/>
<RF>N</RF>
<LTS>01092007 034619</LTS>
<GMT>01092007 094619</GMT>
<TY>DL</TY>
<PM>1</PM>
<PB>3</PB>
<PV>1</PV>
<PR>+.00</PR>
<CY>1</CY>
<DP>+.00</DP>
<DCY>1</DCY>
<AR/>
<AD/>
<AP/>
<AE/>
<AI/>
<ADT>P</ADT>
<TF>N</TF>
<NF>Y</NF>
<PP/>
<EX>0</EX>
<GPS>N</GPS>
<HWID>22E360918290BB425138956C3DDC699D</HWID>
<BF>N</BF>
<ATY/>
<WA>Y</WA>
<CDATE>01092007 095107</CDATE>
<CREATOR>SystemManager</CREATOR>
</BR></BILLING11>
THIS IS THE ACTUAL SCHEMA that I can't get to work…
<BILLING11>
<CARRIER>Midwest Wireless</CARRIER>
<DID>1277</DID>
<GMT>01092007 100007</GMT><br>
<EI>1197459579</EI>
<CID>64</CID>
<ADS>3600</ADS>
<SID>311416418703137</SID>
<NSID/>
<PID>8071</PID>
<PN>QC00080805</PN>
<NM>RingTone JukeBox 2</NM>
<AN>RingTone JukeBox 2</AN>
<MF>9 Squared</MF>
<SN/>
<RF>N</RF>
<LTS>01092007 034638</LTS>
<GMT>01092007 094638</GMT>
<TY>DL</TY>
<PM>1</PM>
<PB>3</PB>
<PV>1</PV>
<PR>+.00</PR>
<CY>1</CY>
<DP>+.00</DP>
<DCY>1</DCY>
<AR/>
<AD/>
<AP/>
<AE/>
<AI/>
<ADT>P</ADT>
<TF>N</TF>
<NF>Y</NF>
<PP/>
<EX>0</EX>
<GPS>N</GPS>
<HWID>79E29862D284E292E4F9A79541636F69</HWID>
<BF>N</BF>
<ATY/>
<WA>Y</WA>
<CDATE>01092007 095107</CDATE>
<CREATOR>SystemManager</CREATOR>
</BR>
<br>
<EI>1197459577</EI>
<CID>64</CID>
<ADS>3600</ADS>
<SID>310005074502771</SID>
<NSID/>
<PID>8071</PID>
<PN>QC00061447</PN>
<NM>FlixTones</NM>
<AN>FlixTones</AN>
<MF>9 Squared</MF>
<SN/>
<RF>N</RF>
<LTS>01092007 034619</LTS>
<GMT>01092007 094619</GMT>
<TY>DL</TY>
<PM>1</PM>
<PB>3</PB>
<PV>1</PV>
<PR>+.00</PR>
<CY>1</CY>
<DP>+.00</DP>
<DCY>1</DCY>
<AR/>
<AD/>
<AP/>
<AE/>
<AI/>
<ADT>P</ADT>
<TF>N</TF>
<NF>Y</NF>
<PP/>
<EX>0</EX>
<GPS>N</GPS>
<HWID>22E360918290BB425138956C3DDC699D</HWID>
<BF>N</BF>
<ATY/>
<WA>Y</WA>
<CDATE>01092007 095107</CDATE>
<CREATOR>SystemManager</CREATOR>
</BR><CT>12838</CT>
</BILLING11>
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.