(Originally published elsewhere in 2016)

My previous post provided a very high level overview of creating an Azure Logic App which uses the Azure Logic Apps Integration Pack to accept XML messages from an HTTP trigger. However we need the XSD and Map file to get the logic app working in terms of XML Validation and Transform.

We are going to quickly create the Integration Project using Visual Studio 2015 for the purposes of this proof of concept.

Download the Azure Logic Apps Enterprise Integration Tools

Download and install the tools from here, and let us create a new Integration Project

Create the Project

In Visual Studio, create a new project by going to New Project, Biztalk and Integration.

20161210createnewbiztalkproject.png- Architect Forward (architectFWD™)

Once created you should have a pretty bare bones project. We’ll create 2 schema files and then the actual map. The map can be created using a designer and the resulting output is an XSLT file used to perform the XML transformation.

In my instance I used an old purchase order schema found on the Microsoft website and created my own Response schema, just to get things moving.

One thing I noted is that I had added my XSD manually and it did not work on the Map designer. Perhaps the Biztalk namespace was not included and could have been the reason. Anyway, it worked fine when creating 2 new schema via the “Add item” and filling in the schema implementation as you need.

20161210newmap.png- Architect Forward (architectFWD™)

After the schema have been created, use “Add Item” to add a new Map. Choose the source schema, then the destination schema and drag and drop your transformation steps. There are many components here and some trial and error will get you what you need. I did try using the Test Map function on the map.btm file, and found that the experience could be richer.

Here is how my map looks

20161210mappingschematransforms.png- Architect Forward (architectFWD™)

After you are happy that it all looks and works as expected, build the project and you should find an xslt file in the build folder. We should now have all the artifacts we need to setup the Logic App and Integration Account in Azure. We’ll do that as part of a separate post.

In closing, you will need the following for the next steps:

  1. The Source and Destination schema (Mine are PurchaseOrder and PurchaseOrder_Res)
  2. The XSLT build from the Map

20161210xslt.png- Architect Forward (architectFWD™)

Move on to part 3 (coming soon) and configure your Azure Logic App to test out the Integration workflow.

Update - part 3 here

Architect Forward (architectFWD™)


Originally published elsewhere on 10 December, 2016.

Quintes van Aswegen

Quintes van Aswegen

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.