BizTalk
Tripped on this one again -- the idea is that the orchestration posts a message directly to a message box and from there it is picked up by subscribers. This wasn't working, then when I saved the message out of the HAT, I realized the routing properties weren't being promoted. Sigh. Luckily this excellent blog article popped up. Right, use a correlation set. I can't believe I always forget that. LOL. And I also needed the tip from the comment -- declare the correlation set instance inside a scope...
Posted On Saturday, November 08, 2008 6:35 AM | Feedback (0)
Note for later: Bug in biztalk mapper with multiple messages. BizTalk mapper does not support multiple input messages where 2 (or more) use the same namespace. I get a compile error on the btm.cs file -- a file I cannot even edit. Workaround: Use two maps. In second one, take the result of the first one, mass copy, plus add the second message. And a *somewhat* related bug report: http://support.microsoft.co...
Posted On Wednesday, October 01, 2008 1:54 PM | Feedback (1)
BizTalk & BRE - sigh - This error seems to happen upon compile when your business rule policy isn't working/is broken and you try to compile your orchestration. update: When adding helper classes to a policy, make sure it and ALL of its dependencies are in the GAC. If at a later date you have even one missing dependency, it will halt your development, make you unable to view the policy, etc
Posted On Monday, September 22, 2008 1:06 PM | Feedback (0)
The message box viewer gives an excellent overview of BizTalk solution including custom tweaks against some "less" documented features. This helped me diagnose an exceptionally high load after we created additional host instances where someone had actually increased biztalk polling interval (but hadn't documented this so it was unknown to me). http://blogs.technet.com/jp... -Jennifer Zouak...
Posted On Monday, November 26, 2007 10:26 AM | Feedback (0)
Installing a BizTalk App can be quite a challenge. You have options of 1) Manual, lots of documentation needed. But then you were going to create docs anyway, right? This is good when you only need to install it once. 2) BizTalk-generated MSI. This is simple and quick to produce. My main issue is that this is not customizable with regard to the application name and product version (think Add/Remove programs) nor can you specific the installation folder. Another huge problem is that *if* the deployment...
Posted On Thursday, November 15, 2007 8:31 AM | Feedback (0)
I was trying to sovle a sticky problem involving someone else's assemblies but not getting very far -- I needed more information such as line numbers. Usually when you invoke a .NET assembly from BizTalk you need to put it in the GAC and this means you are deprived of the symbols (PDB) which would normally sit beside the assembly in the file system. There are some good posts out there but they seem to relate to .Net 1.0 so they didn't quite work. Here's what you do: You can copy the PDB files directly...
Posted On Thursday, November 15, 2007 8:10 AM | Feedback (1)
This month I have had to lookup BizTalk 2006 behaviour for 64 bit architectures for two different clients. It doesn't seem to be well known, but this should be more of an issue in future. Firstly, Microsoft documents BizTalk as supporting 64 bit, and then follows up with a few exclusions: ia64 bit for one, and many of your favorite adapters for another. http://technet.microsoft.co... So if you are going to target 64 bit architecture, be careful with your deployment design...
Posted On Thursday, November 15, 2007 7:59 AM | Feedback (2)
I have the pleasure recently, after working with BizTalk since 2001, of actually implementing a solution using the business rules engine aka BRE as hosted by a BizTalk Orchestration. While the "insight" is fresh, I though I'd jot down my observations. This may be of interest to you if you are evaluating this for use within your solution/organization. BRE uses a different paradigm than typical coding. Now if you are considering BizTalk, then you are probably aware of this already. But even so, although...
Posted On Monday, February 26, 2007 9:12 AM | Feedback (4)
BizTalk error messages are notoriously opaque. I decided to start recording my translations and solutions for these messages because... well because I keep encountering the same ones time and again, my mental buffer is full, and flipping through loads of notes is no longer fun. Error: Unexpected event ("document_start") in state "processing_empty_document". Scenario: This advice applies if you receive this error during receive pipeline xml disassembly processing, and you are using an envelope schema....
Posted On Wednesday, November 08, 2006 8:58 AM | Feedback (1)
If you are new to BizTalk 2006 and you basically aren't sure what's what yet, there is quite the learning curve just to get started. One of the MAJOR hurdles is often just to ensure that your environment is working. Let's face it, there's still a lot of um *bs* getting BTS working. The way that I always *always* start when working with a new environment is to verify it before I start with adding any business functionality. I do this using a “Hello World” strategy. Thanks to the new application...
Posted On Friday, June 09, 2006 7:38 AM | Feedback (1)
Full BizTalk Archive