Webinar Playback: What do we know about Microsoft’s BizTalk Migrator so far?

Microsoft’s announcement of the BizTalk Migrator has heated up the whole topic of Integration Modernisation and migrating from BizTalk to Azure Integration Services.  In this webinar Andrew is joined by Dan Probert, CTO of Affinus and world-leader in this field, to go through the Microsoft announcement and analyse what this means for you.

A look through some of the key screenshots

Conceptual Design

This is the conceptual design of the BizTalk Migrator.  

This illustrates that conversion will follow a pipeline-style execution in a sequence:  We speculate that the sequence will be like this:

  • Discover – finding the BizTalk artefacts
  • Parse – reading the artefacts
  • Analyse – looking at the application and analysing how it will be migrated
  • Report – issuing a report on the migration
  • Convert – converting from BizTalk to AIS
  • Verify – deploying the solution so it can be tested

Design Patterns at Work

This is an example of how a BizTalk receive port might be broken down into components and reassembled as a Logic App.

We think that this draws heavily on Enterprise Integration Patterns, as some of the terms used in the diagram such as Routing Slip and Content Based Router point to these well-established patterns. 

Installing the BizTalk Migrator

The BizTalk Migrator will be installed via Chocolatey, here’s an example of what that might look like (our “artist’s impression”!):

Help Text Shows the Commands Available

This screenshot shows the help (-h) option of the command line, and shows various example commands.

Some example commands are:

  • Migrate – perform all of the migration steps
  • Assess – perform all steps up to the report stage
  • Convert – convert and verify the application
  • Verify – verify a previously converted application

Tool Output Shows What’s Going On

Example output – in this example the tool has been used to run an assessment of a BizTalk application and the output trace shows what has happened.  You can see the components that have been run, including components that look at MSIs, assemblies, binding files and the Application Definition File.

HTML Report Shows Relationships Between Components

In this example we can see some of the report output.  We can clearly see that the BizTalk application has been broken down into its components and there is an attempt to link some of them together.

HTML Report Breaks Down MSI into Components

In this example we can see the report showing the contents of a BizTalk MSI including the CAB files inside the MSI, the BindingInfo file and the resources nested inside the bindings.

Listen to the Audio

Download the Slide Deck

Click the button below to access your own copy of the slide deck.

More on this topic…

Share this post