|
| Copyright © TIBCO Software Inc. All Rights Reserved |
prefix.installation.EZComm.INITIATOR.REQUESTExternal example: AX.BC.BC-ACME.EZComm.INITIATOR.REQUEST
Table 28 Private Message: InitiatorRequest The private process generates the closure message and sends it to TIBCO BusinessConnect, which is required to return this closure contents back in the InitiatorResponse to ensure that the private process can match it with the original Initiator.Request. Note : It works only with Request_Response operations. Note : It works only with Request_Response operations. If set to true, the file reference specified in the filename field is deleted after the completion (successful or otherwise) of the transaction processing. prefix.installation.EZComm.INITIATOR.RESPONSEExternal example: AX.BC.ACME.EZComm.INITIATOR.RESPONSE
Table 29 Private Message: Initiator Response A three-part ID of the form: category/version_number/operation_Name. Code indicating the status of the message. 200 for success. Otherwise, a code that represents the type of error. OK or a description of the cause of the error. The private process generates the closure message and sends it to TIBCO BusinessConnect. TIBCO BusinessConnect is required to return this closure contents back in the InitiatorResponse to ensure that the private process can match it with the original InitiatorRequest.
• For HTTP/s transports, this is the filename that is sent as a file reference from the private process when the Allow override of filename via HTTP parameter check box for the partner is selected.
|
| Copyright © TIBCO Software Inc. All Rights Reserved |