Microsoft KB Archive/830892

From BetaArchive Wiki
Knowledge Base


The Rnmsgtoackall.xml map incorrectly maps the GlobalBusinessIdentifier elements for 3C3 PIP DTDs and for 3C4 PIP DTDs in BizTalk Server Accelerator for RosettaNet version 2.0

Article ID: 830892

Article Last Modified on 12/20/2004



APPLIES TO

  • Microsoft BizTalk Accelerator for RosettaNet 2.0 Enterprise Edition
  • Microsoft BizTalk Server 2002 Standard Edition
  • Microsoft BizTalk Server 2002 Enterprise Edition
  • Microsoft BizTalk Server 2002 Service Pack 1



SYMPTOMS

RosettaNet Implementation Framework (RNIF) 1.1 Acknowledgement messages that are created in response to a RNIF 1.1 Request message for a 3C3 Partner Interface Process (PIP) and for a 3C4 PIP do not contain the expected GlobalBusinessIdentifier attribute.

CAUSE

The GlobalBusinessIdentifier attribute is generated in the RNIF 1.1 Acknowledgement message by the Rnmsgtoackall.xml map file. The Extensible Stylesheet Language Transformations (XSLT) logic in the Rnmsgtoackall.xml map file checks for the presence of the GlobalBusinessIdentifier attribute directly under a BusinessDescription element as follows:

<PartnerRoleDescription> <PartnerDescription> BusinessDescription GlobalBusinessIdentifier



The document definitions that are associated with a 3C3 PIP and with a 3C4 PIP maintain the GlobalBusinessIdentifier attribute directly under a BusinessIdentification element as follows:

<PartnerRoleDescription> <PartnerDescription> BusinessDescription BusinessIdentification GlobalBusinessIdentifier



The document definition that is associated with a 3C3 PIP and with a 3C4 PIP maintain the GlobalBusinessIdentifier attribute in a different location. Therefore, this value is never populated by the Rnmsgtoackall.xml map file when a RNIF 1.1 Acknowledgement message is generated for a 3C3 PIP document and for a 3C4 PIP document.

RESOLUTION

To install the Microsoft BizTalk Accelerator for RosettaNet 2.0 hotfix rollup, visit the following Microsoft Web site:


The BizTalk Accelerator for RosettaNet 2.0 hotfix rollup contains an updated Rnmsgtoackall.xml map file that derives the GlobalBusinessIdentifier value from the "ServiceHeader" section of the document instead of from the "ServiceContent" section. The location of the GlobalBusinessIdentifier attribute in the "ServiceHeader" section is consistent for all RNIF 1.1 document schemas.

Keywords: kbtshoot kbprb KB830892