Create the project in Visual Studio
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
BizTalk Services enables you to:
Create and manage EDI, AS2, and EDIFACT Messaging (Business to Business)
Configure Add Source, Destination, and Bridge Messaging Endpoints to receive and send messages
Use Learn and create Message Maps and Transforms to manipulate data
Using the BizTalk Adapter Service (BAS), you can connect to on-premises LOB applications from the cloud
But how and where do we start creating solutions to achieve each of these business objectives?
For business-to-business messaging using EDI, AS2, and EDIFACT, there is a BizTalk Services portal where you can add your trading partners and create agreements between them. See Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal.
You use the BizTalk Services project system to create a part or all of a BizTalk Services solution. The core element of any such solution is a BizTalk Service project — a collection of items such as XML bridges, BizTalk Adapter Service component, Transforms, and schemas that you can build and deploy to Azure. These items are used together to configure an end-to-end message flow.
For example, a message is sent to an XML bridge, which processes it and sends it over to the BizTalk Adapter Service component, which updates the backend LOB application.
When you create a BizTalk Service project, you generally include one or more of the components from the following list. These components play specific roles in creating your solution:
Bridges: Bridges are message mediation patterns that process the message as it is relayed from the client to the destination endpoint. As part of the message mediation, bridges also extract/promote properties that can be used for message routing/processing.
Sources: These represent the message sources from which a bridge can receive messages. See Add a Message Source to the Bridge.
Destinations: These represent the endpoints where the messages, processed by the bridge, are routed to. See Add a Message Destination to the bridge.
BizTalk Adapter Service: Provides connectivity from BizTalk Services application to on-premises LOB applications such as SQL Server, SAP, Oracle, Siebel, and so on. See Using the BizTalk Adapter Service (BAS).
Schemas: A schema describes the structure of an XML document. Schemas exchange information among applications within an organization or among trading partners.
Transforms: A Transform maps data from one format to another. Transforms present source schemas and destination schemas side-by-side and enable you to define mapping between data elements of different messages. See Learn and create Message Maps and Transforms.
Prerequisites for Configuring a BizTalk Services Application
You must meet the following prerequisites before you can start creating BizTalk Services applications:
Install Azure BizTalk Services SDK to start creating BizTalk Services applications, including extending the reach of your BizTalk Services applications to on-premises LOB applications like SQL Server, SAP, and so on.
You must have a valid Access Control and Service Bus namespace with credentials.