Inbound Request Format

TIBCO BusinessConnect Container Edition - RosettaNet Protocol uses this message class to forward inbound request or notify messages to the responder private process.

 

Class: BCRequestToPP

Installation: prefix.installation.RESPONDER.REQUEST (JMS queue)

Message Fields:

BCRequestoPP: TIBCO BusinessConnect Container Edition to Responder Private Process Message
Message Field Type Required Description
transaction ID String Yes A concatenation of the initiating trading partner’s DUNS ID and the value of the processInstanceIdentifier field in the RNRequestToPP object, separated by the character ’^’.

For example: 123456789^PID000000001

standardID String Yes The string "RosettaNet".
operationID String Yes

A three-part PIP ID of the following format:

PIP/version/activity.

For example: 3A4/1.4/Create Purchase Order.

message FingerPrint String Yes ID derived from processInstanceIdentifier to uniquely identify this incoming request.
isDuplicate String Yes true or false. Indicates that the message contains a duplicate request
closure String No Reserved
operation TimeOut Integer No Time to perform (in seconds).
extraInfo RosettaNet/Request/ RNRequestFromPP Yes RosettaNet protocol specific data. See RNRequestFromPP Object Fields, for formatting information
attachment List Sequence of RosettaNet/Info/ AttachmentInfo No A sequence of attachments. See AttachmentInfo Object on for formatting information.
request String Yes The content of the entire RosettaNet PIP request, without headers and attachments. The request document may also be placed in a file whose path is specified in the fileReference field, leaving this field empty.

See Request and Response Fields for formatting information.

sender RosettaNet/ Info/TPInfo Yes The initiating trading partner. See TPInfo Fields for formatting information.
receiver RosettaNet/Info/TPInfo Yes The recipient trading host. See TPInfo Fields for formatting information. for formatting information.
file Reference String No  

RNRequestToPP Object

Included in the extraInfo field is the RNRequestToPP object. This object contains useful information extracted from the MIME-formatted message. See the following table for a description of object fields:

RNRequestToPP Object Fields
Message Field Type Description
globalUsage Code String The PIP mode extracted from the <GlobalUsageCode> element in the inbound PIP document’s preamble header.
messageSent String The field is formatted in the following way:

YYYY/MM/DD HH:MM:SS.SSS.

For example: 2007/08/30 14:41:35.500.

rnifVersion String

The RNIF version extracted from the <VersionIdentifier> element in the inbound PIP document’s preamble header.

pipCode String The PIP code extracted from the <GlobalProcessIndicatorCode> element of the inbound PIP document’s service header.
pipVersion String The PIP version extracted from the <VersionIdentifier> element of the inbound PIP document’s service header.
pip Transaction String The name of the PIP transaction extracted from the <GlobalTransactionCode> (RNIF 1.1) or <BusinessActivityIdentifier> (RNIF 2.0) element of the inbound PIP document’s service header.
pipAction String The name of the PIP transaction extracted from the ActionControl/ActionIdentity/ GlobalBusinessActionCode element of the inbound PIP document’s service header.
process Instance Identifier String The instance identifier extracted from the ProcessIdentity/InstanceIdentifier (RNIF 1.1) or pipInstanceId/InstanceIdentifier (RNIF 2.0) element of the inbound PIP document’s service header.
transaction Identifier String (RNIF 1.1 only) The transaction’s instance identifier extracted from the TransactionIdentity/InstanceIdentifier element of the inbound PIP document’s service header. RNIF 1.1 only.
transaction AttemptCount Integer (RNIF 1.1 only) Number for the current attempt (first one is 1) extracted from the <AttemptCount> element of the inbound PIP document’s service header.
proprietary Document Identifier String The value of the <proprietaryDocumentIdentifier> element in the inbound PIP document.