14 Sep’15

Azure and Office 365Developing Integration Solutions using Microsoft Azure BizTalk Services

Part 1 – Creating Microsoft Azure BizTalk Services and Deploying Bridge.

Scope:

  1. Creating Microsoft Azure BizTalk Services on Azure Portal
  2. Developing and Deploying BizTalk Bridge on Azure.

Pre-requisite:

  1. Azure Subscription to create BizTalk Service.
  2. Visual Studio for Developing BizTalk Bridge solution.
  3. Windows Azure BizTalk Services SDK (including Microsoft BizTalk Adapter Pack and Microsoft WCF LOB Adapter SDK)
  4. .NET Framework 3.5.1 Features should be enabled
  5. .NET Framework 4.5 must be installed

Background:

Microsoft Azure is a cloud computing platform and infrastructure, created by Microsoft, for building, deploying and managing applications and services through a global network of Microsoft-managed and Microsoft partner hosted datacenters. The cloud services as offered as PaaS (Platform as a Service) and IaaS (Infrastructure as a Service).

Step 1: Creating BizTalk Service

Launch windows Azure portal through URL

https://manage.windowsazure.com (You can create a Trial Subscription)

Go to NEW option at the bottom of the page. Select APP SERVICES → BIZTALK SERVICE → CUSTOM CREATE

1

2

This BizTalk Service Creation web form allows the creation of storage Account Tracking Databases.

After successfully creating the BizTalk Service you get the BizTalk URL. (https://cloudfronts.biztalk.windows.net)

On Clicking the Connection Information Button at the bottom of the page, you get Access Connection Information. This information you need to copy to a notepad to be used during deployment of the BizTalk Bridge solution on Azure.

NAMESPACE

DEFAULT OWNER

DEFAULT KEY

3

4

 

Step 2: Developing the BizTalk Bridge Solution

Launch Visual Studio 2012 and open a new project. Select BizTalk Service Template under folder located BizTalk Services in Visual C#.

Please note BizTalk Services Templates are visible in Visual Studio 2012 only after you install the Windows Azure BizTalk Services SDK. (BizTalk Service Templates are not available in Visual Studio 2013 and 2015 even after installing the SDK)

5

In the Visual Studio solution you need to specify 4 components.

  1. Sources
  2. Bridges (XML One way or XML Reply Request or Pass-Through bridge
  3. Destinations
  4. BizTalk Service URL

Sources can be FTP / SFTP or Service Bus Queue or Subscription.

Destinations have more options like FTP, FTPS, Service Bus Queue, Service end point, Blob Storage etc.

Bridges can be XML one-way or Two way i.e. Reply Request and simple Pass Through Bridge.

Right click anywhere in the empty space in the solution and select Properties. Enter the BizTalk Service URL (Example: https://cfsbtdemo.biztalk.windows.net). We get this URL when we create BizTalk Service in Azure portal.

After placing the source, Bridge and Target blocks, connect them using connector under Bridge in toll box items.

For complex solutions business logic and SCHEMA mapping between source and Target entities can be defined inside the bridges. Custom code can be written here.

6

 

Step 3: Deployment

Save and Build the project and Right click and select deploy. Details like ACS Namespace and Issuer Name (Default – owner) and Shared Secret needs to be entered. ACS NameSpace is the Namespace we got earlier from Azure portal on clicking connection information for the BizTalk service. Shared Secret is the Key “Default Key “

7

Check the status in the Visual Studio output window for the deployed components.

Please Note: Deployment Name needs to be Registered / created on https://biztalksvc12.portal.biztalk.windows.net/default.aspx before deploying your bridge. (You may need Silverlight on to be able to launch this end point URL).

8

Provide the BizTalk Service Name as in Azure portal

ACS Issuer name (Default is owner)

ACS Issuer secret – This is Shared Secret key from BizTalk Service Connection Information in Azure portal.

Once you deploy your bridge, it appears under BRIDGES in Microsoft Azure BizTalk services (MABS) Portal. Rest of the deployed codes appear under “RESOURCES”. If you are using bridge solution to route messages from Azure Service Bus Queue to Destinations like Web service end point, you can track them under Tracking Details.

9

 
In the next article we will explore the integration between the Microsoft Dynamics CRM Online and Azure Service Bus queue. Azure servicebus Queue is one of the sources that Azure BizTalk Services can listen to for Integration requirements. Please note Azure Queues and Service Bus Queues are 2 different type of Queue offered by Microsoft Azure.

 

Written by

Team Member

CloudFronts

One thought on “Developing Integration Solutions using Microsoft Azure BizTalk Services”

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Reading more then 10K records in D3FOE OData API

    11 July’ 2018

    Introduction: We all know Dynamics 365 Finance and Operations has limitation of 10K records to be fetched at a time usi...

    Read more
  • Paging in D365 Customer Engagement v9.0

    10 July’ 2018

    Introduction: The Xrm.retrieveMultipleRecords method is used to retrieve a collection of records in Dynamics 365 Custom...

    Read more
  • Set up Dynamics 365 connection in Microsoft Social Engagement

    10 July’ 2018

    Introduction: This blog explains how to Set up Dynamics 365 connection in Microsoft Social Engagement. Steps to be follo...

    Read more
  • Voice of the Customer failed to install

    10 July’ 2018

    Introduction: Many people face issues in installing Voice of Customer solution on v9 environment and trying repeatedly ...

    Read more
  • Scribe Insight AX as a Web Service Find Block issue

    10 July’ 2018

    Introduction: If we need to look up for any value from AX then we do it by using a Find Block in Scribe Insight Eg: Basi...

    Read more