EDI Tutorial 2 Video :: BizTalk Server 2010 :: Create Trading Partner Profiles

  • Article

The video is available at https://msdn.microsoft.com/en-us/biztalk/video/gg153504.

This is the second video of the BizTalk Server 2010 EDI tutorial. In the first video, we reviewed a simple EDI scenario, and prepared for creating a BizTalk Server EDI solution. This video demonstrates how to create trading partners and business profiles.

I am pasting the transcript of the video here to increase the search hits.

*********************************************************************************************************************************************

This is the second video of the BizTalk Server 2010 EDI tutorial. In the first tutorial, we reviewed a simple EDI scenario, and prepared for creating a BizTalk Server EDI solution. In this presentation, we will create two trading partners (for Fabrikam and Contoso) and business profiles (for Procurement System and Order System).

The video contains the following procedures:

  • Create trading partners and business profiles for Contoso
  • Create trading partners and business profiles for Fabrikam

Create Trading Partners

Like we saw in first video of the EDI tutorial video series, a trading partner, also referred to as a “trading party” or a “party”, is at the root level and forms the base for a trading partner solution. We also saw that business profiles represent the business divisions within an organization. In the EDI scenario for this tutorial, we create two trading partners – Fabrikam and Contoso. We will also create two business profiles, one each for Fabrikam and Contoso. In this scenario, we also assume that of the two trading partners, it’s Contoso that hosts BizTalk Server in their organization and uses BizTalk Server to carry out business communication with Fabrikam.

We’ll start with creating a trading partner for Contoso. Run the BizTalk Server Administration Console, browse to Parties, and create a new party. For the party name, enter Contoso. You don’t need to assign send ports now. Make sure the check box for Local BizTalk processes messages received by the party or supports sending messages from this party is selected. By selecting this check box you declare that Contoso is the trading partner that also hosts BizTalk Server.

You must now create the business profile for Contoso, which is called “Order System”. In the BizTalk Server Administration console, expand the Contoso party. You will see a default business profile, Contoso_Profile, which gets created when you create a party. You may choose to use the same business profile or create a new one. For this tutorial, let’s use the default business profile. So, all you need to do is to rename the business profile to Order System.

At this stage, you can specify the protocol settings for the business profile. By specifying the protocol settings at this stage, you can define what kind of encoding protocol (such as X12) the business profile is going to use to exchange messages. You can do so by clicking the “Add Protocol Settings” button. Alternatively, you can choose to specify the protocol settings as part of trading partner agreement that you will create later. For this tutorial, we will specify the protocol settings as part of the trading partner agreement.

You must now create the trading partner for the partner organization, Fabrikam. While creating the trading partner for Fabrikam, make sure you clear the Local BizTalk processes messages received by the party or supports sending messages from this party check box. By doing so, you declare that the Fabrikam does not host BizTalk Server in its organization. Once again, for this tutorial you can use the default business profile, Fabrikam_Profile, and rename it to “Procurement System”.

This concludes the second video of the BizTalk Server 2010 EDI tutorial. In the next video, we’re going to show you how to use BizTalk Server Administration console to create the send and receive ports. Thank you for watching.

*********************************************************************************************************************************************