Bu içerik dilinizde bulunmamaktadır ancak İngilizce sürümüne buradan bakabilirsiniz.

Building Blocks in B2B Messaging


Updated: November 27, 2015


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:

The key constituents of B2B messaging are the trading partners, business profiles, agreements, and bridges. This article provides information on each of these and how they are implemented in the BizTalk Services Portal. It also provides information about the flow of a typical B2B solution and how the different building blocks work together.

Each participating organization in a business relationship is a trading partner. A business partnership involves two or more trading partners. You can use the BizTalk Services Portal to create a trading partner.

A trading partner’s business profile represents the business divisions inside a trading partner organization. For example, two business divisions, “Payment” and “Shipping”, within a trading partner organization can be represented as business profiles in the BizTalk Services Portal. Profiles include the property settings that are commonly used when configuring agreements between partners, such as the certificates that are used sign and encrypt messages exchanged between the partners.

Certificates uploaded to a partner’s profile are used to sign/un-sign and encrypt/decrypt messages.

A Trading partner agreement is defined as a definitive and binding agreement between two trading partners for transacting messages over a specific B2B protocol. An agreement defines the protocol, and the related properties, that are used by the trading partners for exchanging messages.

A bridge configuration defines the schema of the message to be processed, any transforms that must be used while processing the message, and the endpoints where the message is routed to. Bridges use agreements at runtime. For more information on how a bridge resolves to an agreement, see How do bridges resolve agreements at runtime?

This section details the flow of a typical B2B solution and how the different building blocks work together. This section also lists some best practices for modeling a B2B solution.

  1. Create partners representing all the organizations involved in a business trade. For example, if there are two business organizations involved in a business trade, you must create a trading partner for each of them. For instructions on how to create trading partners, see Manage Partners and Profiles in Azure BizTalk Services.

  2. Creating a partner automatically creates a default profile for the partner. For each business division within a partner organization, create more profile if required. Also, you must create the business profiles not just for the partner representing your organization but also for the partner with which you trade. For more information on creating profiles, see Manage Partners and Profiles in Azure BizTalk Services.

  3. Create agreements between the business profiles. For instructions on how to create agreements, see Create Agreements in Azure BizTalk Services.

  4. Create bridges to process the messages exchanged between the trading partners. See Create an EDI bridge using BizTalk Services Portal or Create an AS2 bridge using BizTalk Services Portal.