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


Chapter 11 Private Messages : Responder Messages

Responder Messages
The following responder messages are described:
Responder Inbound Request — BusinessConnect to Private Process
The responder private process uses this message to handle inbound requests, as shown in Responder Inbound Request.
Even if the incoming message size exceeds the threshold set under
BusinessConnect > Gateway > Gateway Services > HTTP > Transport > Advanced > Data Streaming Threshold (KB) in TIBCO Administrator, the full message, not a file reference, is sent to the private process through RV or JMS.
A new property bc.soap.pp.fileref.threshold is added under BusinessConnect > System Settings > Activated Protocol Plug-ins and properties > SOAP in TIBCO Administrator. The default value is 5MB.
Figure 26 Responder Inbound Request
Subject Name
prefix.installation.SOAP.RESPONDER.REQUEST
Example RV Subject: AX.BC.BC-ACME.SOAP.RESPONDER.REQUEST
Example JMS queue: AX.BC.BC-ACME.RESPONDER.REQUEST
The body element is modified to have appropriate namespaces; for example, if a body element is in a default namespace, it is added to the body element before converting to XML format.
A three-part ID of the form: interface/version/operation_Name.
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 BusinessConnect can match it with the original ResponderRequest message.
Sequence of Attachment
Sequence of SOAP/
Attribute
This field is set to true when the message is a resent transaction.
This field is set to true when this is a duplicate request.
Responder Outbound Response — Private Process to BusinessConnect
The responder private process uses this message to handle outbound responses, as shown in Figure 27.
Figure 27 Responder Outbound Response
Subject Name
prefix.installation.SOAP.RESPONDER.RESPONSE
Example RV Subject: AX.BC.BC-ACME.SOAP.RESPONDER.RESPONSE
Example JMS queue: AX.BC.BC-ACME.RESPONDER.RESPONSE
When the value in the statusCode field is set to under 200 or above 299, the SOAPFault element is sent to the trading partner and the body is ignored even if it contains data. To send the content of the body, the value in the statusCode field must range between 200 and 299.
OK, or the string representing the cause of the error. See statusCode and statusMsg Field Reference.
Identifies the specific value under xop >
tagName > value
if MTOM is selected when sending outbound messages.
If the SOAP MTOM Enabled check box is selected, the value under xop > tagName > value of the private process message must be populated according to the binary data element in the body node. If not, the request is rejected and the outbound process is ended.
If the SOAP MTOM Enabled check box is not selected, and the value under xop >
tagName > value
in the private process is provided, the request is rejected and the outbound process is ended.
MTOM and attachments from the private process cannot be used together. If the SOAP MTOM Enabled check box is selected, and some attachments are also specified from the private process request message, the request is rejected and the outbound process is ended.
When selecting the SOAP MTOM Enabled and Require Content Encryption check boxes to send outbound messages, the binary content which refers to the value under
xop > tagName > value in the private process message is ignored. The encrypted data in the CipherValue element after encryption is used to construct the MTOM attachment.
Sequence of Attachment
BusinessConnect generates a closure message, and sends it to the local private process in the ResponderRequest message 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 BusinessConnect can match it with the original ResponderRequest message.
A three-part ID of the form: interface/version/operation_Name.
Sequence of SOAP/
Attribute
Not used for Responder.Response messages.
The Send Response activity has the SOAPFault element as a part of a body element, and also of the BCResponderResponse element.
When sending a SOAP fault, you can populate it in the SOAPFault element under the BCResponderResponse element or in the SOAPFault element under the body element. Any SOAP fault values specified under the body element are ignored when the values under the BCResponderResponse element are provided.
Responder Acknowledgement — BusinessConnect to Private Process
When the responder BusinessConnect sends a response, the responder BusinessConnect sends an acknowledgement to the local private process if the initiator BusinessConnect returns no error, as shown in Figure 28.
Figure 28 Responder Acknowledgement
Subject Name
prefix.installation.SOAP.RESPONDER.ACK
Example RV Subject: AX.BC.BC-ACME.SOAP.RESPONDER.ACK
Example JMS queue: AX.BC.BC-ACME.RESPONDER.ACK
Table 38 ResponderAck
OK, or the string representing the cause of the error. See statusCode and statusMsg Field Reference.
BusinessConnect generates a closure message, and sends it to the local private process in the ResponderRequest message upon receiving a request for a synchronous request-response operation.

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