Copyright © Cloud Software Group, Inc. All Rights Reserved

Responder Messages

Responder Inbound Request

The Responder private process uses this message to handle inbound requests.

Figure 4 Responder Inbound Request

Rendezvous Subject Name

prefix.installation.standardID.RESPONDER.REQUEST

Example: AX.BC.BC-ACME.B2B-X12.RESPONDER.REQUEST

JMS Queue Name

prefix.installation.RESPONDER.REQUEST

Example: AX.BC.BC-ACME.RESPONDER.REQUEST

Message Name

ResponderRequest

Table 14 ResponderRequest (Sheet 1 of 2)

Field	Type	Required	Description
standardID	String	Yes	B2B-X12, B2B-TEXT, B2B-TRADACOMS, B2B-EDIFACT.
operationID	String	Yes	ID of operation to be performed. Format: interchange_version/group_version/transactionoperation Example: 00403/005010/850
operaionType	String	No	Notify or Synchronous Request Response
transactionID	String	Yes	Unique ID that the Responder TIBCO BusinessConnect generates to associate with an inbound message.
sourceTP	String	Yes	Name of the Initiator of this message.
destinationTP	String	Yes	Name of the Responder to this message.
resend	Boolean	No	Indicates if this request is generated based on re-processing of an inbound EDI document triggered by the resend link from the audit log viewer.
closure	Any	No	Used for the synchronous request-response operation. TIBCO BusinessConnect generates the closure message and sends it to the local private process. If this is a request of a synchronous request-response operation, the private process is required to return this closure contents back in the ResponderResponse message to ensure that TIBCO BusinessConnect can match it with the original Responder request message.
request	String	No	A string representing the message body or TIBCO Rendezvous/JMS representation of an EDI file. This string is the converted EDI information for one transaction in the EDI document that was received from the trading partner. If the option to disable XML conversion for the sending trading partner is disabled, this field is not populated with the XML string.
requestFile	String	No	If the request message is passed by file reference, holds the name of the file. Used when Publish XML Request as File Reference is enabled and the size of the request exceeds the specified threshold value. For more information about publishing requests as file references, see Advanced Tab.
receivedTime	Data Time	No	The original GMT timestamp of the inbound request received by TIBCO BusinessConnect.

Responder Outbound Synchronous Response

The Responder private process sends this message as a response to an incoming synchronous request.

Synchronous request-response operations are supported in B2B-X12.

Figure 5 Responder Outbound Synchronous Response.

Rendezvous Subject Name

prefix.installation.standardID.RESPONDER.RESPONSE

Example: AX.BC.BC-ACME.B2B-X12.RESPONDER.RESPONSE

JMS Queue Name

prefix.installation.RESPONDER.RESPONSE

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

Message Name

ResponderResponse

Table 15 ResponderResponse 

Field	Type	Required	Description
standardID	String	Yes	B2B-X12.
operationID	String	Yes	ID of operation to be performed. Format: interchange_version/group_version/operation Example: 00403/005010/850R
transactionID	String	Yes	The transaction ID of the original request. The private process is required to return the original transaction ID.
encoding	String	Yes	The encoding used in the response. Example: UTF-8
statusCode	Integer	Yes	One of the error codes. See Appendix B, Status and Error Codes.
statusMsg	String	Yes	Represents the cause of the error. In this case, the response might be an error document. See Appendix B, Status and Error Codes.
closure	Any	Yes	TIBCO BusinessConnect generates the closure message, and sends it to the local private process in the ResponderRequest upon receiving a request for a synchronous request-response operation. The private process must return this closure contents in the ResponderResponse message to ensure that TIBCO BusinessConnect can match it with the original Responder request message.
response	Any	Yes	String representing the response message body or TIBCO Rendezvous/JMS representation of a file.
responseFile	String	No	When the reponseFile is very large, this field is populated by the private process in place of the response.

Copyright © Cloud Software Group, Inc. All Rights Reserved