- This topic has 4 replies, 1 voice, and was last updated 8 years, 3 months ago by
.
-
Posts
-
-
I’m looking to send transactions to a new MSMQ location that essentially will be read by SSIS and process the data into SQL Server. This is more of a ‘can-it-be-done’ thing than it is a production consideration, so no need to rack too many brains here, btw.
That being said, when I experimented and pushed out an XML document to MSMQ from SSIS, it was a simple string….easy enough. But now, I’m trying to send an XML document out from Biztalk to the Q that SSIS is to monitor, and I can’t seem to push out the XML in the correct format. I’ve been messing with this for a few days along-side some other tasks, so I may have gone well beyond my thought process and may be trying too hard…that being said, can anybody offer some insight, and if it truly is too easy, feel free to smack me around as well..I can take it. 🙂
-Rich
-
quoute:
I can’t seem to push out the XML in the correct format
What is the “incorrect” format that you’re getting?
Mike
-
I fired out an XML doc to a Q, to see what encoding (not format, sorry) was being used…and then had another SSIS package pick it back up from the same Q, just to test the waters. I’m trying to figure out how to configure my send ports in BTS to output the XML to the Q so that SSIS can read the expected encoding. I tried several of them so far, even the good ‘ol ActiveXMessage formatter equivalent with no results.
-
Rich
If you’re trying the correctly set the message encoding on the outgoing message, you can either set it through the XmlAssembler TargetCharset property, or via the XLANG/S property TargetCharset as follows:
outputMsg(XMLNorm.TargetCharset) = "UTF-16";
Charles Young has a good write-up from BizTalk 2004: http://geekswithblogs.net/cyoung/archive/2004/07/04/7584.aspx
Hope that helps?
Nick.
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.