by Liz Ruffles
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 our CTO Dan Probert is joined by Dr Andrew Rivers, Director at 345 Technology, to go through the Microsoft announcement and analyse what this means for you.
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:
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.
The BizTalk Migrator will be installed via Chocolatey, here’s an example of what that might look like (our “artist’s impression”!):
This screenshot shows the help (-h) option of the command line, and shows various example commands.
Some example commands are:
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.
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.
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.
