When messages are exchanged between the TPI server and the IBM WebSphere adapter for TPI, the TPI server uses a Message Control Document (MCD) to describe both the trading partners involved and the RosettaNet data to be exchanged. The MCD is a TPI-specific XML document that the TPI server uses to process RosettaNet documents. The TPI server converts the information contained in the MCD to a RosettaNet document received from or sent to the trading partner.
The TPI-RNIF data handler simplifies the process of creating and parsing MCDs. It recognizes and manipulates the various RNIF headers, business signals and Partner Interface Processes (PIP) messages, if any, embedded in the MCD. It also usually minimizes the number of business object definitions you must manage when multiple PIPs are used.
The TPI-RNIF data handler determines the appropriate business object definition to which an MCD should be mapped, and it identifies the various RNIF parts, business signals and PIP documents of the RosettaNet payload embedded in the MCD. Once it has identified these parts, the TPI-RNIF data handler internally calls the IBM WebSphere Business Integration Data Handler for XML, which then converts the parts to their appropriate business object types. Therefore, business object definitions used with the TPI-RNIF data handler must conform both to the XML data handler's business object requirements and to the TPI-RNIF data handler's naming conventions described in this appendix.