• Stephen W. Thomas
  • Azure Integration Gurus
BizTalkGurus
  • Home
  • Blogs
    • Stephen’s BizTalk and Integration Blog
    • BizTalk Community Blogs via Syndication
  • Forums
  • Downloads
  • Videos
  • Training
    • Online Training
    • Classroom Training
Select Page

How to Create an Integration Account Project in Visual Studio 2019

by Sandro Pereira | Jun 15, 2023 | BizTalk Community Blogs via Syndication

This post was originally published here

An Integration Account allows you to build Logic Apps with enterprise B2B capabilities by adding various necessary artifacts. It serves as a central repository for managing various integration assets such as schemas, maps, certificates, and trading partner agreements.

While nowadays, Logic App Standard natively supports Schemas and maps (without the need for an Integration Account), and there is a new transformation editor called Data Mapper (still in preview). Logic App Consumption still requires us to use the Integration Account and still uses the “old kind of related BizTalk Server Mapper”.

Pre-requirements

So, for us to create, in our developer environment, Schemas and Maps for Logic App Consumption to be used inside an Integration Account we need to install Azure Logic Apps Enterprise Integration Tools extension for Visual Studio 2019 – unfortunately, there is no support for recent versions of Visual Studio. To do that, we need to:

  • Download and Install the extension from the Visual Studio Marketplace:
  • Or install it directly on Visual Studio by:
    • Open Visual Studio 2019, and on the Extensions menu, select the option Manage Extensions.
    • Search for Logic App, and then from the list, select to download and install the Azure Logic Apps Enterprise Integration Tools.
    • You will probably need to restart Visual Studio.

Create an Integration Account Project

Now that we have installed everything that we need to create a new Integration Account Project, we need to:

  • Open Visual Studio 2019 and on the What would you like to do? window select the Create a new project option.
  • On the Create a new project window, search for Integration Account, and from the list below, select the Integration Account template, then click Next.
  • On the Configure your new project window, do the following configurations and then click Create:
    • On the Project name property, set a proper name for your project.
    • On the Location property, set the path where you want to create the project.
    • On the Solution name property, set a proper name for your project.
      • Note that a solution is a container for one or more projects in Visual Studio.

After that, a new Integration Account project is created where you can create your Schemas, Flat File Schemas, and Maps. To do that, you just need to:

  • Right-click on the project name and then select the option Add > New Item…
  • On the Add New Item window, on the left tree, select the option Logic Apps, and all the possible artifacts for you to create will be present.
    • Select the type.
    • Give it a proper name.
    • And click Add.

Hope you find this helpful! So, if you liked the content or found it helpful and want to help me write more content, you can buy (or help buy) my son a Star Wars Lego! 

Some of the various artifacts that can be added with an integration account are: Schemas: These are standard . xsd files containing the definition of an XML message

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc.

He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.
View all posts by Sandro Pereira

  • Facebook
  • Twitter
  • Google+
  • Gmail
  • LinkedIn

Search this Site:


Recent Posts

  • Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
  • BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
  • BizTalk Oracle Adapter error: The assembly required for type mapping not found.
  • PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
  • Friday (funny) Fact: There is no size limit for the Logic App parameter name

Tweets by AzureIntGurus

Recent Topics

  • Evaluating on the amount of items returned in a message
  • Send and Receive ports problem
  • How to config/costom a WS Security to SOAP header
  • Email attachments – POP3 adapter
  • Calling ASP page from Biztalk Orchestration

  • Home
  • Blogs
  • Forums
  • Downloads
  • Videos
  • Training
  • Facebook
  • X
  • RSS
@BizTalkgurus.com