How to import a custom PIP to the BizTalk Server Accelerator for RosettaNet BTSKInstances table (823198)


The information in this article applies to:

  • Microsoft BizTalk Server Accelerator for RosettaNet, version 2.0

SUMMARY

This article describes how to manually create or import a custom Partner Interface Process (PIP) for use with the BizTalk Accelerator for RosettaNet 2.0.

In the BizTalk Accelerator for RosettaNet 2.0 application, you cannot create or import a custom PIP without using the Partner Agreement Wizard. However, outside the application, you can manually create or import a custom PIP for use with the BizTalk Accelerator for RosettaNet 2.0 without using the Partner Agreement Wizard.

MORE INFORMATION

To manually create or import a custom PIP for use with the BizTalk Accelerator for RosettaNet 2.0, follow these steps:
  1. Download the ZIP file that corresponds to the new PIP. To do this, visit the following RosettaNet Web site:

    http://rosettanet.org

  2. Generate an XML file that contains the list of stored PIPs. To do this, run the script that is described in the following Microsoft Knowledge Base article:

    329082 How to change or reset the PIP templates in the BTSKInstances database

  3. In a text editor (such as Notepad), open the XML file, add a new InterfaceDescription element, and then add the following subelements that are based on the information in the Microsoft Word file or the Adobe Acrobat PDF file for the PIP:
    • ProcessIndicator - The value for this subelement appears on the title page (for example: 2C2).
    • ProcessCode - The value for this subelement appears on the title page (for example: Request Engineering Change).
    • ProcessVersion - The value for this subelement appears on the page that has the link to the download for the ZIP file for the PIP (for example: R01.00).
    • Sync - The value for this subelement is 0, 1, or 2:
      • A value of 0 means 0A1.
      • A value of 1 means that only Async is supported.
      • A value of 2 means that both Sync and Async are supported.
      Most PIPs have a Sync value of 2.
    • Actions - This subelement contains individual Action elements.
    • Action - This subelement contains an ActionCode element.
    • ActionCode - The value for this subelement is the value (or values) for "Business Action in FSV" in table 4-2 (for example: Engineering Change Request Action). The ActionCode element contains the following subelements:
      • SchemaName - The value for this subelement is the name of the DTD file for the corresponding ActionCode, where .xml is used instead of .dtd and the value is prepended with the path of the corresponding segment and cluster (for example: ServiceContent/cluster2/segmentC/2C2_MS_R01_00_EngineeringChangeRequest.xml). You can create this schema file in BizTalk Editor by importing the corresponding DTD file.
      • DTD - The value for this subelement is the name of the DTD file that is included in the downloadable ZIP file that corresponds to the ActionCode in table 3-4 (for example: 2C2_MS_R01_00_EngineeringChangeRequest.dtd).
      • Role - The value for this subelement depends on the number of ActionCode subelements for a process indicator and the names of the ActionCode subelements.

        Typically, if there is more than one ActionCode, there is an Initiator/Responder relationship between them. The Responder ActionCode subelement contains one of the following words:
        • Acceptance
        • Confirmation
        • Response
        If there is only one ActionCode, there is only an Initiator role.
    A completed InterfaceDescription element that contains the associated subelements appears similar to the following:
    <InterfaceDescription>
<ProcessIndicator>2C2</ProcessIndicator> 
<ProcessCode>Request Engineering Change</ProcessCode> 
<ProcessVersion>R01.00</ProcessVersion> 
<Sync>2</Sync> 
<Actions>
<Action>
<ActionCode>Engineering Change Request Action</ActionCode> 
<SchemaName>ServiceContent/cluster2/segmentC/2C2_MS_R01_00_EngineeringChangeRequest.xml</SchemaName> 
<DTD>2C2_MS_R01_00_EngineeringChangeRequest.dtd</DTD> 
<Role>Initiator</Role> 
</Action>
<Action>
<ActionCode>Engineering Change Confirmation Action</ActionCode> 
<SchemaName>ServiceContent/cluster2/segmentC/2C2_MS_R01_00_EngineeringChangeConfirmation.xml</SchemaName> 
<DTD>2C2_MS_R01_00_EngineeringChangeConfirmation.dtd</DTD> 
<Role>Responder</Role> 
</Action>
</Actions>
</InterfaceDescription>
  4. Write the XML file that contains the updated list of PIPs back to the BTSKInstances database. To do this, use the script that appears in the following Knowledge Base article:

    329082 How to change or reset the PIP templates in the BTSKInstances database

  5. To verify that each the PIP was uploaded correctly, run the Partner Agreement Wizard.
    • If the PIP was uploaded correctly, it is available in the list of existing PIP definitions that appears in the Partner Interface Process dialog box of the Partner Agreement Wizard.
      -or-
    • If a PIP contains information that is not valid, use the script from the Knowledge Base article that appears in step 4 to write the original PIP templates list XML file back to the BTSKInstance database.
Modification Type:MajorLast Reviewed:11/4/2004
Keywords:kbhowto KB823198 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.