Forum Replies Created
-
AuthorPosts
-
Even though SQLXML 4 is installed – you must install SQLXML 3.0 from here: http://www.microsoft.com/downloads/details.aspx?familyid=51D4A154-8E23-47D2-A033-764259CFB53B&displaylang=en
After that restart your VS and get started!
Thanks. Yes ESB can be installed from the msi.
But to get the ESB Portal to work – it requires to compile the solution. The portal part itself does not have an MSI.
Maybe you want to see the book written by Richard Seroter about BizTalk 2009. You can find it at Amazon (http://www.amazon.com/SOA-Patterns-BizTalk-Server-2009/dp/1847195008)
Also, there is a free chapter about the SQL adapter in 2009 from this book.
I think you need to use the BizTalk Explorer Object model. It would allow you to specify this. It is not command line, but you could wrap the code to do it inside of a console app that takes command line switches.
Have you tried manually configuring a port, then exporting the binding for it and comparing that with what you are building in your string?
I would guess that your code to build the xml is missing a > or < sign or something like that that makes the xml invalid.
Hello Pon,
Seems to me that there are two different problems:
You: Having problems with the UAT Database and not with the DEV Database.
We: Having NO problems with the UAT Database but with the DEV Database after it has been cloned from the UAT Database.
Robbish.
After some investigations I found out, that it seems, there is a size limit for the content of CDATA. Is there a way to extend the max. lenght of the CDATA content? Or is this a restriction of BizTalk?
Thx for this hint. It was part of the solution, but it seems there is another problem.
Here is what I produced:
<?xml version=”1.0″ encoding=”utf-8″?>
<ns0:Daten xmlns:ns0=”http://IMS_FlatFileHandler.SOB_Protokoll“>
<Record>
<source>Ennshafen Rechnungseingang</source>
<record_count>33</record_count>
<status>abgeschlossen</status>
<Summe>6579</Summe>
<datetime>2009-06-17T15:15:21</datetime>
<Text><![CDATA[<ns0:IMS_Invoice xmlns:ns0=”http://IMS_Schemas.PxB_RG_Standard” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”><position><ims_customer_no>123456</ims_customer_no><invoice_no>13210</invoice_no><invoice_date>”28.02.2009″</invoice_date><information xsi:nil=”true”></information><count_pos>33</count_pos><pos_no>1</pos_no><text>”Hub”</text><price_per_unit xsi:nil=”true”></price_per_unit><amount>1</amount><value>25,5</value><ims_order_no
….some more lines….xsi:nil=”true”></information><count_pos>33</count_pos><pos_no>33</pos_no><text>”Hub”</text><price_per_unit xsi:nil=”true”></price_per_unit><amount>1</amount><value>25,5</value><ims_order_no xsi:nil=”true”></ims_order_no><informations><container_id>”EISU4601611″</container_id><container_length>”20″</container_length><inbound_date>”27.02.2009″</inbound_date><inbound_code>”W”</inbound_code><outbound_date>”02.03.2009″</outbound_date><outbound_code>”L”</outbound_code><text>Turn-In: “202479” / Turn-Out: “” / Tage: 4</text></informations></position></ns0:IMS_Invoice>]]></Text>
<content>
</content>
</Record>
</ns0:Daten>I can produce this manually, but in the BizTalk Applikation it produces an error like “Value in field <Text> illegal”. (I use the german version, so sry about this lausy translation.
As I’m no XML-Guru [;)], I can’t find my fault. Maybe you can see the problem.
Thx in advance
You can install ESB from MSI.
Hi
ExplorerOM is being used by the ESB Guidance 1.0.
Does this mean that ESB Guidance simply cannot be used in a 64 bit environment?
Yes you can!
Encode the XML you wish to put in a field as let’s say Base64String. This is in a case you don’t need to see received XML visually, or for another reasons.
Or save it as CDATA[…] – look for the solution in internet.
I want to put the whole received XML Dokument (processed from a pipeline, as it is a flatfile before) into the protocol XML document.
Here is the schema of the XML protocol file:
<xs:element name=”Record“><xs:element name=”source“ type=”xs:string“ /><xs:element name=”record_count“ type=”xs:int“ /><xs:element name=”status“ type=”xs:string“ /><xs:element name=”Summe“ type=”xs:decimal“ /><xs:element name=”datetime“ type=”xs:string“ /><xs:element name=”Text“ type=”xs:string“ /><xs:element name=”content“ type=”xs:string“ /></xs:sequence></xs:complexType></xs:element>I I would like to put the received XML-File into the element “content”, if possible. Maybe it would be even better to put in the received flatfile there, but I can’t find a way to grap this information after using the pipeline for disassembly.If you are retrieving the file from an non-Biztalk web service and sending to another non-Biztalk web service then the easiest way would be to Base64 encode the file stream into an Xml node of the Soap message. Biztalk would not need to decode this data, just send it to the other web service that would decode the base64 back to a file stream.
Alternatively you could use the WCF Adapter and MTOM to move the file payload. This would be more complicated but faster – smaller messages and no base64 encoding/decoding.
Do you wish to put the original Xml message into the element as a string or as an Xml element?
If the former you can do this in an orchestration:XmlDocVariable = InputMessage;
OutputMessage.FileDataDistinguishedField = XmlDocVariable.OuterXml;If the latter then you can use a map.
sry, forgot to register.
so I’m the poster
-
AuthorPosts