Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 8 Private Messages : Responder Messages

Responder Messages
Responder Inbound Request
The Responder private process uses this message to handle inbound requests. A ResponderRequest message is created for each transaction in each interchange from the received inbound EDI document. A ResponderInterchange message is created for each interchange from the received inbound EDI document.
Figure 17 Responder Inbound Request
Rendezvous Subject Name
prefix.installation.standardID.RESPONDER.REQUEST
Example: AX.BC.BC-ACME.X12.RESPONDER.REQUEST
JMS Queue Name
prefix.installation.RESPONDER.REQUEST
Example: AX.BC.BC-ACME.RESPONDER.REQUEST
Message Name
ResponderRequest
ID of operation to be performed. Format: interchange_version/group_version/transactionoperation
If the Log Raw EDI Segments to File check box for inbound transactions is enabled for the trading partner, the full path of the stored location is included in this message class. See TransactionInfo.
X12 and EDIFACT have the following attributes in common: Trading Partner Name, operationID, transactionName, whole transaction (only the ST to SE segments for X12, UNH to UNT segments for EDIFACT), host initiates flag, interchange control number, group control number, and transaction control number.
TEXT has the following attributes: Trading Partner Name, operationID, transactionName, whole transaction, host initiates flag.
TRADACOMS has the following attributes: Trading Partner Name, operationID, transactionName, whole transaction, host initiates flag, interchange control number.
Controlled by the Enable EDI Validation check box.
Responder Inbound Interchange
TIBCO BusinessConnect sends the ResponderInterchange message to the private process when it receives an interchange from the trading partner.
Rendezvous Subject Name
prefix.installation.standardID.RESPONDER.INTERCHANGE
Example: AX.BC.BC-ACME.X12.RESPONDER.INTERCHANGE
JMS Queue Name
prefix.installation.RESPONDER.INTERCHANGE
Example: AX.BC.BC-ACME.RESPONDER.INTERCHANGE
Message Name
InboundInterchangeLoggedToFile
Contains a constant value: EDI/Inbound/Interchange
sourceFile
ResponderInterchangeComplete
TIBCO BusinessConnect sends the message ResponderInterchangeComplete to the private process upon receiving an interchange from the trading partner when the option under General>Inbound>Enable Interchange Complete Message is enabled.
This message also marks the completion of this interchange validation and conversion.
Rendezvous Subject Name
prefix.installation.standardID.RESPONDER.INTERCHANGE.COMPLETE
Example: AX.BC.BC-ACME.X12.RESPONDER.INTERCHANGE.COMPLETE
JMS Queue Name
prefix.installation.RESPONDER.INTERCHANGE.COMPLETE
Example: AX.BC.BC-ACME.RESPONDER.INTERCHANGE.COMPLETE
Message Name
InboundInterchangeComplete
Contains a constant value: EDI/Inbound/Interchange
sourceFile
Responder Outbound Synchronous Response
The Responder private process sends this message as a response to an incoming synchronous request.
Figure 18 Responder Outbound Synchronous Response
Rendezvous Subject Name
prefix.installation.standardID.RESPONDER.RESPONSE
Example: AX.BC.BC-ACME.X12.RESPONDER.RESPONSE
JMS Queue Name
prefix.installation.RESPONDER.RESPONSE
Example: AX.BC.BC-ACME.RESPONDER.RESPONSE
Message Name
ResponderResponse
ID of operation to be performed. Format: interchange_version/group_version/operation
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.
Responder Acknowledgment to Partner
The Responder TIBCO BusinessConnect sends this notify message to the private process to indicate the success or failure of the posting of an acknowledgment to the Initiator.
If the Responder TIBCO BusinessConnect failed to successfully post the acknowledgment to the Initiator, the statusMsg field indicates the cause of the error.
Rendezvous Subject Name
prefix.installation.standardID.RESPONDER.ACK
Example: AX.BC.BC-ACME.X12.RESPONDER.ACK
JMS Queue Name
prefix.installation.RESPONDER.ACK
Example: AX.BC.BC-ACME.RESPONDER.ACK
Message Name
TransactionAckToTradingPartner
Table 30 ResponderAck 
The transmissionID property is provided in the ResponderAck messages to indicate to the private process when it is scheduled for batching.
ID of operation to be performed. Format: interchange_version/group_version/operation
Note   The value of this field is configuration for the outbound transport: it is the URL (or URI) pointing to the location where the acknowledgment was sent out.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved