FixEncoding Pipeline Component for BizTalk 2004
I've just uploaded a version of my Fix Encoding Pipeline Component I had written for BizTalk Server 2006 that has been retro-ported to BizTalk Server 2004.
The code is not exactly the same and it is not so pretty, but mostly because the .NET Frramework 1.1 does not have functionality to enumerate supported encodings (not even half baked like v2.0), so I hardcoded a list of encodings for the dropdown, which I hope are supported :-).
Keep in mind you'll need to GAC the component in order for the custom UITypeEditor to work!. Enjoy.
March 24th, 2006 in
BizTalk
Hey Tomas,
I tried to download the component, but I get a 404. Looking forward to seeing the solution, and thanks agiain for the time.
-Rich
Hey Tomas,
I’m still dead in the water…no clue what I’m doing wrong. May I send you an email on my details and maybe we can grind a little bit to figure something out that I may be missing?
Thanks,
-Rich
Hi Tomas,
I try to work with your tools for biztalk 2004 but it doesn’t work.
I have a pipeline and create a flatefile and use the fix encoding after the flatfile assembler. The encoding makes no changes.
Thanks,
Bernd
Bern,
If this is on a send pipeline, you should pick up the updated version of the component which includes the SetEncodingComponent, and put it *before* the flat file assembler (i.e. in the Pre-Assemble stage of the pipeline).
Hi Tomas,
Me again
I was curious, if I use your component in a Send pipeline component, can I essentially send my outgoing messages to MSMQ where the consuming applications that expect the ActiveXMEssageFormatter format will still work? I was thinking of adding the component to my ‘Pre-Assemble’ and follow that up with the Xml Assembler in the ‘Assemble’ area and that *should* set the encoding correctly, I hope?
-Rich
Rich,
You can certainly use my component in a send pipeline, but be sure to use the SetEncodingComponent I mention here (http://www.winterdom.com/weblog/CommentView,guid,8eb8776b-4de3-421f-a620-eecda74d07dc.aspx) or just set the properties in your orchestration as necessary. That said, if you’re using the ActiveXMessageFormatter with BizTalk 2004, you’ll be in trouble, because the MSMQ adapter in 2004 doesn’t expose a way to set the BodyType property that’s needed for the ActiveXMessageFormatter to understand that the message is encoded as a string (see http://www.winterdom.com/weblog/2006/01/31/MSMQActiveXFormatterStringsAndBizTalk2006.aspx)
Thank you, sir….and there lies my issue, the subscribing applications do expect the ActiveXMessageFormatter and I am on BTS 2004. Ah well, I’m using a custom .NET component called within an Expression shape now, but looks like I’ll have to wait until I can get BTS upgraded.
Thanks again!
-Rich