People in the Integration space would always remember the BizTalk stickers that they receive from Sandro and here it is for BizTalk 2020.
Download it here
As the new version of BizTalk Server is released and you wanted to take advantage of the new features and improvements, you need to device the strategy for seamless migration. In this section, Sandro is explaining why you should upgrade your BizTalk platform in general.
Here are a few reasons:
There are two options,
This is the easy option as most of them run BizTalk on the Azure VMs. There are options of high availability and, they can be hosted in various regions.
This is completely moving out of BizTalk. All the BizTalk related artifacts will be migrated to the Azure services. It is a complete redesign of the Integration solution. For example, there will be no Message Box and therefore Service Bus needs to be used to persist the messages. It is a difficult option even with the new BizTalk Migration Tool.
BizTalk Server has a rapid release cadence of major versions every 2/3 years with radical changes. Azure is completely different. BizTalk server with the long release history is very stable. Eg: Features that are introduced in 2004 are being used as a core feature until the current version of BizTalk.
But the cases are completely different in Azure,
There are two options available to migrate to the latest version of BizTalk Server (2020)
This is the first option and it’s too risky to do it directly in the production environment. And most of the integrations people won’t choose this option for the upgrade.
Eg: In the previous version BizTalk Server 2013 R2 they might be using the different OS (Windows Server 2012 R2,2012,8.1, 7 SP1), SQL Server but to migrate to the latest version needs an upgrade of that supported software’s as well mentioned in the below screenshot.
There are few constraints like the SQL Adapter that has been deprecated, TIBCO Enterprise Message Adapter has been removed and the RosettaNet has issues in BizTalk 202 for which the hotfix needs to be installed for smooth functioning.
This is migrating the solutions without any non-mandatory changes. The .Net framework needs to be changed, the deployment properties need to fix and the solution to be rebuilt.
This needs to be done on the analysis of the business requirements and what needs to be improved on the solution side. This requires a more prolonged version of testing a lot of improvements would be added and for the integration between different teams.
With his experience of more than 16 years working in BizTalk, Sandro shares the statistics on the effort of different migration options. You can get all those different metrics and the amount of time it would take during the migration represented in the below screenshot.
The effort to Migrate artifacts/components for BizTalk Server
There are some pain points while migrating the BizTalk Server artifacts/components in the source code level.
In this section Sandro is explaining about how much migration effort it would take from different versions of BizTalk Server to latest version (2020).
BizTalk Server 2013 to 2016 – These are easy migrations.
BizTalk Server 2010 – Depending on the features and solutions it can give you some work. But normally, if everything is well done it is easy.
BizTalk Server 2009 to 2004 – It is little difficult. For the normal and basic stuffs, it could be fine. It requires some work to do the EDI and Maps.
BizTalk Server 2002 to 2000 – All the stuffs need to re-write everything from the scratch. As a better option, you can migrate to Logic Apps.
BizTalk360 is used by 650+ enterprise customers in 40+ countries across the globe. With BizTalk360, you can better operate and monitor your BizTalk Server environment. Our team has worked on the v10 release for close to 1 year to completely refresh the user interface. Also, based on the customer’s feedback from our BizTalk360 feedback portal, some new features were developed. You can get a 30 days trial version of BizTalk360 and explore the product yourself or arrange for a personal demo of the product.
Hope the insights on the Microsoft BizTalk Server 2020 gives a clear picture on the migration path. Sandro and Tom Canter are working on the book on the BizTalk2020 Migration which would be available soon.