Wow. BizTalk is always full of surprises.
Stephen W. Thomas has an explanation here.
Photo by Marcelo Leal on Unsplash
Creating or Input Multiple Messages from or to Biztalk Maps
Sure, we all know how to do that by know, right?
Funny thing is, all the blog entries I’ve seen like the ones here and here, end up creating a new map, usually situated in the root of your assembly (or event worse, create temporary orchestrations to do that). In order to move it to another folder in your project you’ll have to edit the XML contained inside the map since it contains relative paths to the schemas mapped (and watch out for those namespaces).
[Read More]
Biztalk Listen Shape
I’m no Scott Woodgate, but I think I know a fair amount about BizTalk. However, it seems that I never recognized what the Listen shape actually does (you don’t see this mentioned very often btw.). Turns out that this little shape can solve many of the problems we’re currently having, mainly correlation issues, like situations where the message you are waiting for might never arrive, keeping your orchestration in a dehydrated state, waiting forever.
[Read More]
Now this is jewel in my Biztalk Toolbox
If your BizTalk orchestration is published as a web service and something goes awry in your orchestration a specific exception might not be thrown to your web service, but rather it will throw ApplicationTimeOutException.
I was prepared just to live with it, until I found the following jewel here.
Turns out you can have custom SOAP faults returned in your orchestration. Who would’ve known?
Photo by jesse orrico on Unsplash