Initiator Response

This message shows whether the InitiatorRequest has been successfully sent to your trading partner.

JMS Queue Name

prefix.installation.INITIATOR.RESPONSE

Example: AX.BC.BC-ACME.INITIATOR.RESPONSE

Message Name

InitiatorResponse

InitiatorResponse

Field

Type

Required

Description

standardID

String

yes

The string CMI

transactionID

String

no

A unique ID to identify the current request/response in CMI Protocol. If not specified, it is automatically generated.

batchID

String

no

Batch ID of the executed request

operationID

String

yes

CMI Operation Schema version and the operation name in the following format: version/Category/operationName
For example: 1.0/Write/UpdateParticipant.

sessionID

String

no

A sessionID to identify the current session.

response

String

no

An XML string representing the message body or TIBCO Rendezvous/JMS representation of an XML file. The CMI XXXRESP element contains either the response body or an ERRORMsg element:

<UPDATEParticipantRESP>
<Status code="100" message="OK" />
</UPDATEParticipantRESP >
or
<UPDATEParticipantRESP>
<ERRORMsg code="403" message="Data      Violation" desc="Exception …"/>
</UPDATEParticipantRESP>"

fileReference

String

no

The URL to the response saved as a file in the TIBCO BusinessConnect shared folder

closure

String

yes

A unique identifier used between the private process and BusinessConnect to match up the Request and Response documents in a transaction. The Response to this Request or Notify message from BusinessConnect contains the same ID in the closure field.

Note: TIBCO BusinessConnect cXML Protocol does not enforce nor verify the uniqueness of message closures.

statusCode

String

no

A code value indicating success or failure.

statusMsg

String

no

A status message indicating the status of the request sent from BusinessConnect to the private process.