How to use an XSD-based PIP with the BizTalk Accelerator for RosettaNet 3.0 (915090)

SUMMARY

A Partner Interface Process (PIP) document defines business processes between trading partners. The Microsoft BizTalk Accelerator for RosettaNet 3.0 supports the use of all current RosettaNet PIPs in BizTalk Server 2004 RosettaNet solutions. Many PIPs that are available from the RosettaNet.org Web site are Document Type Definition (DTD) schemas. The BizTalk Accelerator for RosettaNet 3.0 documentation describes how to create projects that use DTD-based PIPs. However, many of the newer PIPs that are available on the RosettaNet.org Web site are XSD schemas. This article describes how to use XSD-based PIPs.

MORE INFORMATION

These steps use the "PIP 7C7: Notify of Semiconductor Test Data" PIP that is available on the RosettaNet.org Web site. For more information about the "PIP 7C7: Notify of Semiconductor Test Data" PIP, visit the following RosettaNet.org Web site:

http://www.rosettanet.org/Rosettanet/Rooms/DisplayPages/LayoutInitial?Container=com.webridge.entity.Entity%5BOID%5BB3756C626980B745992D3D6E41EF2BD7%5D%5D

To import the "PIP 7C7: Notify of Semiconductor Test Data" PIP, follow these steps:

Download the "PIP 7C7: Notify of Semiconductor Test Data" PIP from the RosettaNet.org Web site.
Unzip the .zip file to a folder on the hard disk.

Note The files that are used in this example are located in the XML subfolder.
Create a new BizTalk Server 2004 project in Microsoft Visual Studio. For example, create a BizTalk project named PIP7C7.
Use Windows Explorer to copy the Domain folder, the Interchange folder, the System folder, and the Universal folder from the folder that you created in step 2 to the root folder for the PIP7C7 project.

Note Rename any files in the System folder that contain the ".System" string. Rename these files to "._System". If you do not rename these files, you may receive an error message that is similar to the following:
The type or namespace name 'SerializableAttribute' does not exist in the class or namespace 'PIP7C7.System'
Review the .xsd files in each folder to make sure that the <schema> TypeName property and a root node TypeName property are not the same. For example, the PartnerIdentification.xsd schema uses the PartnerIdentification TypeName property for the <schema> node and for the PartnerIdentification root node. To resolve this issue, click the schema in Solution Explorer, click Properties Window on the View menu, and then modify the TypeName property. For example, click PartnerIdentification.xsd in Solution Explorer, click Properties Window on the View menu, and then modify the TypeName property. If the TypeName properties for the <schema> node and a root node are the same, you may receive an error message that is similar to the following:
This schema file has a TypeName that collides with the RootNode TypeName of one of its root Nodes. Make sure that they are different.
Build and then deploy the project.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.