Search Results

Terminology

TIBCO Cloud Integration uses specific terminology to identify the purpose of the message, that is exchanged between a service provider and a service consumer.

Terms Used for SOAP Messages

The following table describes the terms used to describe a SOAP message.

Term Description
ServiceRequest A request message received by a service provider
ServiceReply The response message sent by a service provider
ReferenceRequest A request message generated by a service consumer
ReferenceReply A response message received by a service consumer

SOAP Headers

Refer to the following table for the terminology used to described different configurations that can be used to create a SOAP Header.

Term Description
Described Described denotes that the WSDL message definition used to create a SOAP header is available in the concrete WSDL.
Undescribed Undescribed denotes that the WSDL message definition used to create a SOAP header is not available in the concrete WSDL.
Bound Specifies that the SOAP header definition is the part of the same WSDL message, that is also used to create a SOAP body. In such cases, a WSDL message contains multiple parts. Some parts are defined to describe SOAP headers and others are defined to describe the SOAP body.
Unbound Specifies that the SOAP header definition is not a part of the same WSDL message, that is also used to create a SOAP body
Note: Based on the definitions in the SOAP Headers table, SOAP headers can be categorized into any of the following three types of configurations:
  • Described bound headers
  • Described unbound headers
  • Undescribed unbound headers

SOAP Attachments

Refer to the following table for SOAP attachment types and their relevant description.

SOAP Attachment Types Description
Described Bound Attachments In this configuration, a part of the input or output WSDL message of type base64binary is configured as an attachment. In a concrete WSDL, the attachment is described as a mime part of the multipart message.
Undescribed Unbound Attachments None of the parts of the WSDL input or output message is configured to be an attachment. The concrete WSDL does not indicate whether an attachment is in the input or output message.

Attachment mapping is done at the Binding Configuration under Context Mapping (Request/Response)