![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Figure 24 Initiator Outbound Requestprefix.installation.SOAP.INITIATOR.REQUESTExample RV Subject: AX.BC.BC-ACME.SOAP.INITIATOR.REQUESTExample JMS queue: AX.BC.BC-ACME.INITIATOR.REQUEST
Table 34 Initiator Request A three-part ID of the form: interface/version/operation_name. The private process generates a closure message and sends it to BusinessConnect. BusinessConnect is required to return this closure contents back in the InitiatorResponse message to ensure that the private process can match it with the original InitiatorRequest message.This field is not available for JMS messages. In JMS header fields, closure is populated as JMSCorrelationID. If this field is present, the hostName field must contain the domain identity. If this field is not present, the default domain TPname is used. Identifies the specific value under xop >
tagName > value if MTOM is selected when sending outbound messages.Note:
• 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.See Configuring General Properties for a Partner on how to select SOAP MTOM. Specifies the required values in the saml node if SAML assertions are used when sending outbound messages.If you use SAML assertions in conformance with NHIN/esMD Authorization Framework, provide all the required values in the saml node from the private process. Errors occur if any of the required values is missing.See Request Action Tab on how to configure SAML assertions in conformance with NHIN/esMD Authorization Framework. Sequence of Attachment Sequence of SOAP/
Attribute Sequence of SOAP/
Attribute A synchronous response is sent from the responder BusinessConnect to the initiator BusinessConnect and forwarded to the local private process, as shown in Figure 25.Figure 25 Initiator Inbound Responseprefix.installation.SOAP.INITIATOR.RESPONSEExample RV Subject: AX.BC.BC-ACME.SOAP.INITIATOR.RESPONSEExample JMS queue: AX.BC.BC-ACME.INITIATOR.RESPONSE
Table 35 Initiator Response 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. OK, or the string representing the cause of the error. A three-part ID of the form: interface/version/operation_name The same value that was in the transactionID field of the initiator request. The private process generates a closure message and sends it to BusinessConnect. BusinessConnect is required to return this closure contents back in the InitiatorResponse message to ensure that the private process can match it with the original InitiatorRequest message.This field is not available for JMS messages. In JMS header fields, closure is populated as JMSCorrelationID. 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 response.
The Receive Response activity can receive a SOAP fault or any valid XML document as a response. Therefore, if the Parse XML Payload check box in the Configuration tab in private process is selected, the body element can have either the schema for the response, or the SOAPFault element.To get an appropriate response, the root element has to be configured in TIBCO Administrator, and also the schema has to be present for that operation. If no schema is defined for the response, only the SOAPFault element is displayed. This behavior is the same as in the case of the Send Response activity when sending a response.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |