Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.
If you're brand new to Logic Apps, then we suggest getting started here:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
In the previous steps we created an BizTalk Services bridge that receives the purchase order message from the customer, maps it to an X12 850, then routes it to a purchaseorder blob container. We also created an X12 agreement using the BizTalk Services Portal to receive an X12 850 purchase order message, the message is then sent to the Fourth Coffee restaurant. In this step, we use an Azure worker role that polls the purchaseorder blob container. It then sends the X12 850 purchase order blob to the X12 send bridge that is deployed as part of the X12 agreement.
This topic does not go into the details of creating an Microsoft Azure worker role. You can download the BlobPollerRole worker role sample from https://go.microsoft.com/fwlink/p/?LinkId=390152. You must make the following changes to the role configuration to use it in your environment.
Prerequisites
Make sure you have the Azure SDK for .NET is installed on the computer where you are using the worker role. You can download the SDK from https://go.microsoft.com/fwlink/p/?LinkId=378265.
Update the worker role configuration
Make the following changes to use the BlobPollerRole worker role in your Azure subscription.
Open the BlobPollerRole solution and in the Solution Explorer, expand BlobPollerRole, expand Roles, and then double-click BlobPollerWorkerRole to open the properties for this role.
On the Settings tab, make the following changes to the configuration properties.
ACSAddress
Provide the ACS URL associated with your BizTalk Services subscription.
IssuerName
Provide the issuer name for the ACS namespace.
IssuerKey
Provide the issuer key for the ACS namespace.
PipelineAdderss
Enter the pipeline endpoint where the blob poller must direct the message after reading from the blob. For this tutorial, this must be the endpoint where the EDI X12 send agreement is deployed. You can get the endpoint from Send Settings tab (Inbound URL view) of the X12 agreement you deployed earlier. The endpoint is typically in the format https://mybiztalkservice.biztalk.windows.net/default/Agreements/<id>/Send.
ContainerName
Enter the blob container where the X12 850 purchase order messages are dropped. For this tutorial, enter this value as purchaseorder. You created this container in the earlier steps.
CloudStorageAccountConectionString
Select the ellipsis (…) against the property and in the dialog box, enter the storage account name and the account access key. Select the option to use HTTPS connections, and then select OK.
ContentTypeValue
For content type, enter application/xml.
Save changes to the project.
Right-click the solution name in the Solution Explorer, and then select Build.
After the build completes successfully, right-click the BlobPollerRole in the Solution Explorer, then select Package. In the dialog box that appears, for Service configuration, select Cloud; and for Build configuration, select Release.
Once the operation successfully completes, you will see that two files are created in the \BlobPoller\bin\Release\app-publish directory. In the next step, you upload these files to your Azure subscription to deploy the worker role.
Deploy the worker role on Azure
Open the Azure classic portal, and from the command bar, point to New, Compute, Cloud Service, and then select Quick Create.
Enter a URL for the worker role, select a region where the role will be deployed, and then select the checkmark.
Select the cloud service you created, select the Instances tab, make sure the Production view is selected, and then select Upload from the command bar.
In the Upload a Package dialog box, do the following:
Provide a deployment label.
For Package, browse to the \BlobPoller\bin\Release\app.publish location, and select the service package file (.cspkg).
For Configuration, browse to the \BlobPoller\bin\Release\app.publish location, and select the cloud service configuration file (.cscfg).
Select the checkbox to deploy the worker role even if it contains a single instance.
Select the checkbox if you want to start the worker role after it is uploaded.
Select the checkmark. Once the worker role is deployed, it will start polling the blob you specified in the configuration, until you stop the role from the Azure classic portal.