Recently at my work we’ve started using SSO Affiliate Applications to store credentials for Receive Locations and Send Ports to avoid either having the credentials in the Bindings (which is insecure) or having to re-enter the credentials after each release (which causes releases to take too long). I won’t go into details how we do that in this post, however as part of documenting this ability I went through all the adapters to see which could use SSO Affiliate Applications and which couldn’t.
Below a list of know bugs, issues, & other quirks* of BizTalk 2013 R2 (mainly CU3) and Visual Studio 2013 (update 4) , but I will update with fixes as the CUs come out or when I know about a new issue, so if you have another one I will add it (and link to it if you have a blog about it) if you let me know. This in addition to the ones listed by Microsoft on Known Issues in Installation, Configuration, and Deployment
* My definitions for classifying these are
Bug: Causes negative impact and no known work around or requires a lot of effort to work around.
Issue: Causes negative impact but has an easy or quick work around.
Missing: A feature that BizTalk doesn’t have that would make our life easier.
Quirk: Something strange or unusual but does not cause a negative impact so far as known.
I got this strange error from the WCF-WebHttp sending a payload to a web service bound to a receive location.
Worth a read if you want to know what one of the major new features of BizTalk 2016 is.
The new LogicApp adapter for BizTalk Server 2016 was recently released as an add-on for the CTP2 edition. Here are some more details from Microsoft: Today, Friday 8th July 2016, we have uploaded a new package BizTalk 2016 Adapter for Logic Apps to Connect. The package is available to download for use with BizTalk Server […]