The official announcement An important milestone in enterprise integration – launch of Microsoft BizTalk Server 2016 by Frank Weigel Principal Director, Program Management
Update: The BizTalk 2016 Azure VM is now available in the old Azure portal but not yet in the new portal the download files are avaiable on MSDN & My Visualstudio for Standard, Enterprise & Branch, and now also Developer Edition.
Also the What’s New in BizTalk Server 2016 has been updated, what is new has not changed substantially from previously, however what is interesting there is what they have removed or marked as deprecated.
One of the major news in BizTalk Server 2016 is the full support for SQL AlwaysOn Availability Groups (AGs). When Microsoft announced this, the crowd cheered, and they moved on to the next slide. There are, however, some bits you should be aware of before deciding on your High Availability (HA) architecture for BizTalk.
SQL Server 2016 is the first (and only) edition to support AlwaysOn for BizTalk Server 2016. The reason is lack of support for MSDTC between BizTalk’s SQL Server databases and other transactional resources. For this reason, High Availability for the database layer in BizTalk scenarios has traditionally been solved by using Windows Server Failover Clusters (WSFC), typically with an active-passive configuration.
First of all, you need to run BizTalk Server 2016 Enterprise, SQL Server 2016 Enterprise, and Windows Server 2016 (or 2012 R2 with KB3090973).
As you may be aware of…
View original post 450 more words
One of the most frustrating aspects of working with BizTalk maps does not involve complex maps or functoid usage, or how to call external assemblies, but rather how to run a code compare against previously checked-in .btm files. Often times I want to merely check what changes were made in in the map against a […]
With BizTalk you sometimes have to open up large XML files either as input, or after they have been parsed by a flat file schema, or as the output from a map. Opening it with Visual Studio or other tools is very slow and sometimes to makes them crash.
The Cumulative update package 5 for BizTalk Server 2013 is out, kb 3194301
A mixed bag of fixes in this CU including two fixes for issues caused by two previous CUs.
3165515 & 3167704 were also in CU 4 for BizTalk 2013 R2 and 3142269 was in CU3 for R2, but some of the others may still have to be released in another CU for Biztalk 2013 R2 if they are an issue. Continue reading
Link to video
Colin Dijkgraaf and I presented this on Integration Monday today. In this session we showed why the WCF-WebHTTP adapter requires some workarounds. We used BizTalk 2016 Tap release to demonstrate these workarounds. The presentation and PowerPoint presentation can be downloaded from here.