Setting up a new BizTalk Server environment on the Azure IaaS with multiple Azure Virtual Machines (VM) involves a lot of steps and prerequisites. I have explained them in this blog.
Firstly, sign up for a new Azure subscription or add your Live ID as the co-admin in the Azure subscription if one already exists.
After the co-admin/sys admin privileges, you can choose to administer the Azure subscriptions in these ways: a) Azure PowerShell cmdlets b) Azure Management Portal.
I have used the Azure management portal for provisioning all cloud entities as it is more convenient and a time saver. Below is the architecture diagram that explains the BizTalk environment in Azure IaaS.
May 2014 marks the release date of BizTalk Server 2013 R2. The iteration provides an abundance of new features that includes JSON support, adapter updates, accelerator updates, and a new snap-in application.
BizTalk Server 2013 R2 incorporates the BizTalk JSON Schema Wizard and JSON decoder/encoder. The JSON Schema Wizard provides support to generate XSD schema from a JSON instance. The JSON decoder/encoder components are used with custom pipelines. More information can be found here.
The Service Bus (SB) Messaging adapter now supports Shared Access Signature (SAS) authentication, this feature permits interaction with on-premises edition of Service Bus Queues, Topics, and Relays. Ultimately, this bridges connectivity between Windows Azure and on-premises BizTalk servers. To learn more visit this link.
In addition, the Secure File Transport Protocol (SFTP) adapter now enables two-factor authentication and has the option to specify a temporary folder to support uploading/downloading….