On 27th October Microsoft finally announced the RELEASE of the BizTalk Migrator! 345 together with partners Affinus have been working with Microsoft since the start of the private preview, so we know this tool better than anyone else. Get up to speed with the experts as we take you through the easiest BizTalk-to-Azure conversion you’ve ever seen!
In this episode Andrew and Dan take you through the test scenarios that ship with the BizTalk Migrator and delve in more detail into the components that are actually generated by the migration tool.
Here is a slide of the components that are potentially generated by the BizTalk Migrator:
This shows that what gets generated is a palette of components that you can use to build just about any integration application in Azure.
Now we look at the components generated to deliver an XML messaging solution:
As you can see from this, the components that are used are:
- Service Bus – a topic to facilitate publish and subscribe messaging.
- XML Processor – decodes the XML and establishes the message type.
- XML Validate – ensures the XML conforms to schema.
- XML Translate – replicates maps used in send and receive ports.
- Receive Port (FILE) – a Logic App that contains a FILE trigger, replicating a BizTalk receive location.
- Send Port (FILE) – a Logic App that sends a file using the FILE connector.
- Topic Subscriber – a Logic App that has a Service Bus trigger, that polls for and subscribes to messages on Service Bus.
- API Connections – as all these components are serverless cloud components they need API connections configured to route between them.