(Originally published elsewhere in 2016)
My previous posts part 1 and part 2 provided a very high level overview of the Azure Logic App workflow and the steps to create a new Integration project in Visual Studio. We will now look at the setup in Azure to get all the services talking.
Create the Azure function
I created an Azure function container, and deployed a function from a template using this link
Create the Logic App
Really easy, just log into the Azure portal and create a new Logic App here. Once that’s done don’t do anything in the Designer, we can do that after having created and configured the Integration Account.
Create the Integration Account
The Integration Account is part of the Enterprise Integration Pack, used to store all the integration schema, maps and accounts for your specific integration requirements.
Click New -> Market Place -> Everything and search for “Integration Account”. Create the account by completing all the necessarily fields.
Link the Integration Account to the Logic App
Associate the Integration Account with the Logic App to hook up all the integration bits. In your Logic App, find and configure the Integration Account under Settings
I have very quickly created Partners, Agreements, Schema and Maps for the purposes of getting the workflow running Take a look at the documentation to see what is required. In particular I used the xsd schema and the xslt map built in the Integration Project I created in part 2.
Create the workflow and link the integration artefacts
Now open the Logic Apps designer and drag in the 4 actions from part 1. Those would be an HTTP Request, XML Validation, XML Transform and HTTP Response action respectively.
Configure the XML Validation step to use the Body and specify the schema name specific to this action.
Configure the XML Transform step to use the Azure function and Azure function container you’ve created as well as the same Body variable, and specify the map (the resulting xslt file from the Biztalk integration project).
Finally configure the HTTP Response to return the output (The transformed XML) to the caller.
Give it a spin
Once again, trigger the workflow by submitting valid XML from either Postman or curl. Take a look at the Run result in the Overview blade of the Logic App and it should show you a successful flow through each action. I hope the 3 part series has helped give you an idea of how to use this new technology in Azure. I continue to learn and hope that my notes here help somewhat.
Originally published elsewhere on 17 December, 2016.
24+ years experience in solving business problems and maximising opportunities through technology in a variety of industries, public and private sector internationally. I founded architectFWD™ to provide knowledge and trusted advice in the areas of strategy, technology, cloud and digital to enable organisations to become Digital Leaders.