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 ......
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 ......
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 ......