To support RosettaNet messaging, WebSphere Business Integration Connect provides two sets of ZIP files called packages. The RNIF packages consist of Document Flow Definitions required to support the RNIF protocol. These packages are in the B2BIntegrate directory.
For RNIF V1.1
For RNIF V02.00
The first package in each pair provides the Document Flow Definitions required to support RosettaNet communications with participants, and the second package provides the Document Flow Definitions required to support RosettaNet communications with back-end systems.
The second set of packages consists of PIP document flow packages. Each PIP document flow package has a Packages directory containing an XML file and a GuidelineMaps directory containing XSD files. The XML file specifies the Document Flow Definitions that define how WebSphere Business Integration Connect handles the PIP and define the exchanged messages and signals. The XSD files specify the format of the PIP's messages and define acceptable values for XML elements in the messages. The ZIP files for 0A1 PIPs also have an XML file that the hub uses as a template to create 0A1 documents.
The PIPs for which WebSphere Business Integration Connect provides PIP document flow packages are:
For each PIP, there are four PIP document flow packages:
Each PIP document flow package follows a specific naming convention so that you can identify whether the package is for messages between WebSphere Business Integration Connect and participants or between WebSphere Business Integration Connect and back-end systems. The naming convention also identifies the RNIF version, PIP, and PIP version that the package supports. For PIP document flow packages used for messaging between WebSphere Business Integration Connect and participants, the format is:
BCG_Package_RNIF<RNIF version>_<PIP><PIP version>.zip
For PIP document flow packages used for messaging between WebSphere Business Integration Connect and back-end systems, the format is:
BCG_Package_RNSC<Backend Integration version>_RNIF<RNIF version>_<PIP><PIP version>.zip
For example, the BCG_Package_RNIF1.1_3A4V02.02.zip is for validating documents for version 02.02 of the 3A4 PIP sent between participants and WebSphere Business Integration Connect using the RNIF 1.1 protocol. For PIP document flow packages for communicating with back-end systems, the name of the package must also identify the protocol used to send the RosettaNet contents to the back-end systems. See the Enterprise Integration Guide for information on the packaging used for these messages.