May 20, 2011

BizTalk 2010 EDI : Parties/Party Migration

Parities cannot be directly migrated from order version to BizTalk 2010. Because,  Trading Partner Management (TPM) has been re-engineered in BizTalk 2010. You have to use BizTalk Server Party Migration Tool.

Party Creation in 2010 is more logical & practical than 2006 R2.

New changes are:

  1. We have to create a party (Trading Partner) along with a business profile. Business Profile is analogue to the business divisions in an organization where can have multiple. Each business profiles define parameters for B2B messaging like identifiers, Encoding formats, Protocol  settings.
    Figure 1
  2. In order to do B2B messaging, we have to define agreement(s) between trading partners. This is very easy to use and understand. 
    Figure 2

    As of Figure 2, once you select the second party (number 3 in the picture)  two more tabs on the dialog (number 6) where you defines the interchange and transaction set settings based on the protocol selected. 

    If you have created protocol settings when creating party, you can select them or leave      –None- to override them. (number 5)

May 19, 2011

BizTalk 2010 Error: Schema referenced by Map ‘<map name>’ has been deleted.

When my BizTalk 2006 R2 applications going to be migrated to BizTalk 2010, I did test run on my test server( BizTalk 2010 on Windows 2008R2 64bit).

Then I choose one of simple live-running application to test with, and I got following error in BizTalk administration console.

TITLE: BizTalk Server Administration
Schema referenced by Map 'Map name goes here' has been deleted. The
local, cached version of the BizTalk Server group configuration is out of date.
You must refresh the BizTalk Server group configuration before making further
changes. (Microsoft.BizTalk.Administration.SnapIn)
For help, click:

This is yet another message from BizTalk with no help at all.  I could not be able to refresh whole BizTalk Group\Applications Node in the BizTalk Administration console. I spent couple of hours ,while scratching my head, to find a solution.

Solutions like, restarting BizTalk service, Administration console, etc did not work. But I found solution (not my own) which is really works though it is not recommended.

The solution is SQL,

   2: -- Run bellow queries against BizTalkMgmtDb database.
   3: -- You can find the related item here
   4: SELECT * FROM bt_mapspec
   5: -- Replace with correct itemid value
   6: DELETE FROM bt_mapspec WHERE itemid =165 


One of blog post suggests, it could be the reason when the Map and references Schemas are in separate assemblies. I can agree with it, i believe , in this application the map and its source schema in two separate assemblies.

Control Properties in MEC

When we want to keep some parameters in the MEC we often use “.properties” file.  But alternatively we also can use Control properties in th...