Gib 2021 - Intro to BizTalk Migrator
Download as PPTX, PDF0 likes312 views
The document discusses a tool called the BizTalk Migrator that helps migrate BizTalk applications to Azure Integration Services. It summarizes the tool's capabilities like discovering and parsing BizTalk artifacts. It also discusses what is and isn't supported when migrating things like adapters, pipelines, and orchestrations. The document provides installation instructions and highlights differences between the original and migrated applications that users may encounter.
Gib 2021 - Intro to BizTalk Migrator
- 1. Dan Toomey Escaping the T- Rex Deloitte @daniel2me A brief look at the BizTalk Migrator
- 2. Coming up: Deep Dive
- 4. Why migrate from BizTalk? • Freedom from version bondage • Licensing costs • Maintenance costs • Support windows • Skills shortage • Scalability • Modern architecture
- 5. What about parity? BizTalk Server Azure Integration Services Messaging Engine Azure Service Bus Receive / Send Adapters Logic Apps Connectors Azure Functions Event Grid Orchestration Azure Logic Apps Azure Durable Functions Schemas & Maps Integration Account Liquid Templates Pipelines Logic Apps Azure Functions Business Rules Engine ?? BAM ??
- 6. The BizTalk Migrator tool • Command line utility for migrating BizTalk applications to Azure Integration Services • Plug-in architecture • Open source • Capabilities: • Discover/Parse • Analyse • Report • Convert
- 7. Supported • Adapters: • File • FTP • HTTP • Pipelines: • XmlReceive • XmlTransmit • PassthruReceive • PassthruTransmit • Pipeline components: • XmlDisassembler* • XmlAssembler* • XmlValidator • JsonDecoder • JsonEncoder • FlatFileDecoder • Orchestration entities: • Variables • Ports/Port Types • Receive Shapes • Send Shapes • Construct Shapes • Transform Shapes • Transforms in Receive Ports/Send Ports • Property Promotion and Demotion in pipelines • Generates placeholders for unsupported orchestration shapes • Creates a library of common services and Logic Apps that can be used by any integration application (e.g. BizTalk.System application) *Most common usage only
- 8. Not supported • Any adapter not listed in the last slide (e.g. WCF Adapters) • Envelope handling (XmlAssembler/XmlDisassembler) • Recoverable Interchange handling (XmlDisassembler) • Inline C# • Complex Orchestrations • Correlation/Convoys • EDI/Accelerators
- 9. What do I need? • For installing and running the tool: • Windows 10 or Windows Server • Chocolatey (https://chocolatey.org/) • For installing and running the output: • Azure CLI • Active Azure subscription • Windows PowerShell or PSCore (use latest version!)
- 10. Installing the tool • Install with Chocolately in PowerShell • Use the --pre flag
- 11. Converting an application Optional parameters: • Target integration environment (Consumption| ISE) • Subscription ID • Target primary/secondary region • Unique deployment ID • Etc.
- 12. Differences from BizTalk • Flat File Decoding : Uses the FlatFile Encode/Decode Integration Account actions. These have a small number of known compatibility issues, especially around the suppression of empty nodes. • No Subscribers Found : In BizTalk, if a message is published and no subscriber exists, BizTalk throws an exception. Service Bus does not do this: instead the message is published, and if no Subscriber has picked up that message after a given length of time, the message is sent to the Dead Letter queue • Unknown Schemas : Slightly different defaults for handling scenarios where a message is published but no Schema can be found. In general, these scenarios are allowed: the message will be published, but because there is no MessageType property set, it is likely that there will be no subscribers. • Json Encode/Decode : as with BizTalk, Newtonsoft's Json.NET library is used to handle conversion. Due to licensing issues (and the fact this is an open source project), this is NOT the exact code that BizTalk uses (i.e. accustom JSON formatter for serialization/deserialization). This means that there will be cases where the JSON emitted (for XML->JSON scenarios) may be slightly different than what BizTalk emits. • Orchestration Exception Handling : Logic Apps have no equivalent to the try/catch exception blocks used in BizTalk Orchestrations. The tool does not even attempt to migrate them (at the moment). Instead, the Orchestration flow is wrapped in a Scope, and standard Logic App RunAfter functionality is used to check if there were any errors. If you need to execute specific code depending on error scenarios, you'll need to manually add this.
- 13. Sample Scenario: Orchestration with HTTP Request-Response Messaging Engine SQL Server databases BizTalk System Application Orchestration 2-way Receive Port Receive Location HTTP Adapter Map 2 Pipelines Receive Send A P P P L A T F O R M B I N D I N G F I L E
- 14. Sample Scenario: Orchestration with HTTP Request-Response Message Bus API Management, Function Apps, Integration Acct, Logic Apps, Key Vault, App Insights, Storage, App Config, etc BizTalk System 13 Logic Apps, 3 API Connectors, Service Bus 2 API Connectors (Service Bus) PO Processor Subscription Req/Resp Port Subscription 3 Logic Apps Purchase Order Receive Purchase Order Process Request/Response Port R E S O U R C E G R O U P S A P P P L A T F O R M
- 15. Problems you may encounter • Maximum string length for names • https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name- rules • Names are generated from concatenated sub-components, which can be lengthy • FIX: Search & replace (e.g. “UK South” “uks”) • Duplicate references when multiple applications contain the same .Net types or port names • FIX: Run the MSIs through the migrator separately • Existing resources/SKU levels and deployment errors • Free Integration Account, free Azure App Configuration exists already (only 1 allowed per sub) • FIX: Modify the deployment scripts to use the existing resources • Unsupported scenarios • FIX: Manually edit the converted application to include the missing functionality
- 16. References • The BizTalk Migrator tool: https://github.com/Azure/aimtool • The BizTalk Migrator User Guide: https://github.com/Azure/aimtool/blob/main/docs/user-guide/README.md • Chocolatey: https://chocolatey.org/ • Azure CLI installer: https://docs.microsoft.com/cli/azure/install-az • PowerShell Installer: https://github.com/PowerShell/PowerShell • Maximum lengths for Azure resource names: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules • Flat File Decoding and Empty Nodes: https://docs.microsoft.com/en-us/archive/blogs/david_burgs_blog/wheres-my-node-logic-apps-flat-file-decode-beware-suppress-empty-nodes- unintended-effect • Solentive InRule: https://www.solentive.com.au/inrule-business-rules-engine/ • Atomic Scope: https://www.atomicscope.com/
- 17. Key Runaways Takeaways • Apples vs. Oranges: re-architecting for the cloud • Jumpstart only: you’ll still need to write code • Highly extensible & open source
- 18. Thank you!
Editor's Notes
- #5: Zona Research concluded in 2000, “The T-Rex is Loose!”
- #7: Discover/Parse - pull out the BizTalk resources (currently BizTalk exported MSI(s) only). Analyse - look at what BizTalk resources we have, and what can be migrated and build a model of the AIS target. Report - Generate a report outlining what BizTalk resources were found, and what can be migrated. Convert - Generates a series of ARM templates and Azure CLI scripts, generates Logic Apps representing orchestrations.