You configure the TPI-RNIF data handler through data handler
meta-objects. The required properties listed below are specific to the
TPI-RNIF data handler. However, since the TPI-RNIF data handler
internally extends the existing XML data handler functionality, see the
Data Handler Guide for information about additional meta object
properties required by the XML data handler.
Table 7. TPI-RNIF data handler required meta object properties
Property | Description | Required | Default Value |
---|---|---|---|
TopBOPrefix | Resolves the wrapper business object for a given service content
document. Sample values include
RNETOBJand CIDXOBJ. | No, but recommended | None |
BOPrefix | Like TopBOPrefix, but converts the RNIF message parts (such the Preamble,
Service Header, etc.) embedded in the MCD to business objects.
Sample values include
RNETand CIDX | No, but recommended | None |
PIPSpecificSignals | List of semi-colon delimited doctypes for which the data handler should include the PIP identifier when resolving the wrapper business object name. | No | None |
ClassName |
| Yes | com.crossworlds.DataHandlers.text.tpi_rnif_mcd2 |