Additional Data Objects

TPInfo (RosettaNet/Info/TPInfo) and AttachmentInfo (RosettaNet/Info/AttachmentInfo) are additional complex types that are commonly used by some or all of the private process message classes.

TPInfo Fields

See the following table for detailed information of the fields:

TPInfo Fields
Field Type Description
id String The identifier of the trading partner. By default, RosettaNet uses the 9-digit DUNS numbers
locationID String Used to support multiple destination URL for remote trading partner.
domain String The domain for this id. Currently there is only one domain (DUNS), so this field is optional.

AttachmentInfo Object

Field Type Description
content-type String The attached data type. For example: application/binary.
content-id String The order of this attachment is the list of attachments in the following format:

<attachment:number>

disposition-filename

String

The filename of the attachment. This field correspondsto the filename parameter in the MIME header’s content-disposition field. If you do not supply a value in an outbound message, TIBCO BusinessConnect™ Container Edition - RosettaNet Protocol generates one automatically. If an inbound public message does not contain the filename parameter in the attachment MIME header’s content-disposition field, then TIBCO BusinessConnect Container Edition - RosettaNet Protocol does not include this field when forwarding the attachment to the private process.

content Binary The content of the attachment.

file Reference

String

In BCRequestFromPP and BCResponseFromPP The absolute path to the attached file you wish to use. You may use this field instead of the content field if the attachment is too large or for any other reason. This field takes precedence over the content field. In BCRequestToPP and BCResponseToPP The absolute path of the file containing the attachment. .