none
BizTalk Server EDI deployment framework with parties re-initiates InterchangeControlNumber from lower value RRS feed

  • Question

  • We have BizTalk Server 2010 installed and as regular practice we export and import the binding files for all BizTalk application while new releases. We don't have specific rule for EDI in our BizTalk Server deployment framework.

    Using  BizTalk Server deployment framework with parties, re-initiates InterchangeControlNumber from lower value. This creates issue of duplicate document posting as InterchangeControlNumber is used as identifier.

    How can deployment resets the InterchangeControlNumber ?

    Do we have any solution for this?

    Tuesday, March 4, 2014 9:22 PM

Answers

  • Do you really need to export/import the TPM configuration for each release?  My first advice would be to export the TPM settings purely as a backup but don't reimport them.

    Importing any bindings is really a delete/add so when you import, you're essentiall creating new, albeit identical, parties and agreements.

    If you really, really have to import the TPM settings, I think your only option is to note the last set of control numbers, then after the bindings import, go to eash Agreement and set the Lower Bounds to lastcontrolnumber+1.  Once a new set of EDI has been generated, you can set the Lower Bound back to 0, or whatever the previous value was.

    • Marked as answer by Pengzhen Song Wednesday, March 12, 2014 9:27 AM
    Wednesday, March 5, 2014 4:52 PM