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
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.
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.