BizTalk Server 2013 R2 was released last week and one of the biggest questions lot of existing BizTalk Server customers have is whether to upgrade/migrate to 2013 R2 or stay in the current version. The answer to this question will depend on various factors, let’s try to understand the scenarios that can potentially require or force you to do the upgrade.
Before going into the details let’s take a look at 2 important piece of information, the history of last few versions of BizTalk Server and what’s new in BizTalk Server 2013 R2. Because these two factors are very important before we make the decision of whether to upgrade to latest version
BizTalk Server history
- <<previous versions>>
- BizTalk Server 2006
- BizTalk Server 2006 R2
- BizTalk Server 2009
- BizTalk Server 2010
- BizTalk Server 2013
- BizTalk Server 2013 R2
What’s new in BizTalk Server 2013 R2
At a very high level these are the key features that are added in this release.
- Support for Windows Server 2012 R2, SQL Server 2014, Visual Studio 2013
- Updates to SB-Messaging adapter
- Updates to the WCF-WebHttp adapter
- Updates to the SFTP adapter
- Updates to HL7 accelerator
For the complete information please refer to Microsoft release notes
. Technically you can migrate to BizTalk Server 2013 R2 seamlessly if you are in the last 2 versions of BizTalk (2010 or 2013), but the decision to upgrade is not always made purely based on technical reasons. Let’s see some scenarios.
Scenario #1: Upgrade based on your platform requirements
This scenario is something you cannot avoid and will force you to upgrade to BizTalk Server 2013 R2. Every enterprise will have an internal platform upgrade story both for Windows Server and SQL Server. The organisation may be currently running on Windows Server 2008 and every 5 years once they might have a platform upgrade across the company. When such things happen they will create a dependency matrix and if they identify any product that can be moved to latest platform, then they will ask the relevant teams to start the initiative. If such scenario happens then you’ll be forced to migrate to BizTalk Server 2013 R2. A similar story can happen for SQL server upgrade across the company.
Scenario #2: Upgrade based on your current version
Based on the current version of BizTalk server you are running in your organisation, you may be forced or it may be a good idea to upgrade to BizTalk Server 2013 R2. The below table gives the BizTalk Server product support lifecycle information
with dates for end of both main stream and extended support. As you can see 2006, 2006 R2 and 2009 versions are already out of main stream support
||Support End (Mainstream)
||Support End (Extended)
|BizTalk Server 2006
|BizTalk Server 2006 R2
|BizTalk Server 2009
|BizTalk Server 2010
|BizTalk Server 2013
|BizTalk Server 2013 R2
There are lot of disadvantages being in extended support,
- Non-Security hotfix support will require extended hotfix agreement, purchased within 90 days of mainstream support ending
- You incident support will be chargeable
- You cannot make warranty claims
- You cannot request design changes and feature requests
You probably do not want to run your business on limited support, so it’s better to upgrade if your current version is already in extended support or your mainstream support is coming .
Scenario #3: Upgrade based on new features
BizTalk Server 2013 R2 is a small incremental release and it doesn’t come with lot of features. In fact there are no new features, it’s only updates to few of existing ones like SB Messaging adapter, WCF-WebHttp (with good support for JSON), SFTP and HL7 accelerator. We cannot see any compelling reasons to move to BizTalk Server 2013 R2 based on the features alone.
Scenario #4: Upgrade based on your current projects
Most of the time the cost of migrating from one version of BizTalk server to another is not the BizTalk server software cost, because typically you’ll be either covered with annual support assurance (SA) or you’ll have enterprise agreement package (EAP), which will allow you to upgrade and do a true up cost at end of the period.
The biggest cost factor is your functional testing efforts. Even though Microsoft (or any software vendor for that matter) will claim the upgrade will be seamless and will not effect anything. Chances are, something will get broken. If you look at the stack, you are upgrading lot of things Windows, SQL, .NET, BizTalk etc. at one go and you need to be super careful.
The best situation for you to plan for your upgrade and reduce the cost is to do it along with your project plans. If you have a big release coming, and if you are already planning for lot of functional testing, use that as an opportunity to migrate to new version.
If somebody claims their software/tool will magically help you on the upgrade process be cautious. There is no magic bullet here, no one will understand the complexities of the legacy systems you are connecting and their underlying limitations. Only your QA team can warrant that after verifying their test cases.
Scenario #5: What if we are in the process of buying BizTalk Server
In this case, it’s kind of a no-brainer decision, you just buy the latest version of the product i.e BizTalk Server 2013 R2. Having said that we have seen companies using the policy of always using “Latest Version – 1
” formula. They don’t want to risk with some unknown potential problems and wanted to stay with the version that’s in the market for a while. If you are in that situation, it’s perfectly fine to go with BizTalk Server 2013. But keep in mind BizTalk Server 2013 will not run (or supported) in Windows Server 2012 R2 and SQL Server 2014.
Please leave your comments if you have any other reasons.