In order to create a business object structure that is compatible with the TPI-RNIF data handler, you must create three types of business object definitions.
Only one MCD business object definition is needed. Create it using the XML Object Disvovery Agent (ODA), and use the MCD XSD from your TPI server installation as the input. Be sure that the business object prefix you specify for the XML ODA is the same as what you specify in the TPI-RNIF data handler meta object. See the section, "Using an XML ODA to create business object definitions" in the Data Handler Guide.
With most MCD business object definitions, you will need to complete one additional step using the Business Object Designer tool. Use this tool to modify the application-specific information of the attribute
MessageControlDocument.ROOT.ManifestInfo.MessageContentInfo.Body.Body
so that it is of the type "cdata." For example,
mcd:Body;type=pcdata;notag
should be modified to
mcd:Body;type=cdata;notag
One business object definition is needed for each type of service content message you plan to exchange, and one preamble and service header business object is needed for each RNIF version you plan to support. Include the RNIF version number in the BOPrefix, such as
RNET_2_0
. Use the XML ODA to create these business object definitions as well.
Name the wrapper object according the naming conventions described earlier, and then add the MCD envelope business object, the appropriate RNIF header business objects, and a signal or PIP-specific business object, if needed.
You must also define a child meta object to provide routing information required by the adapter for TPI. SeeChild meta-object attributes.