Reference Binding - Request Context

Request Context enables you to map data from the request message to the Get Context activity.

Data Source

Displays the data source schema tree for the input context parameters. All elements in this tree are available to drag and drop into the XPath Expression field.

The following elements are populated from the request message:

Elements of Request Message Description
Transport Properties Transport related information for HTTP headers when the Transport is HTTP, or JMS properties when the Transport is JMS, are populated from the request message. For more information about the transport properties, see Transport is HTTP and Transport in JMS tables.
Headers The header of the request.
Undescribed Headers Undescribed headers from the request message.
mimeEnvelopeElement Information about the attachements that are present in the request message. Individual attachment information is populated under one mimepart element.
Note: If the attachment size increases the threshold value configured at the binding level, the file name of the serialized attachment is populated.
mimeHeader This element contains the mime header for each mimePart. Mime headers can contain the following information:
  • content-disposition — To suggest a filename for an attachment, use "*;filename=<filename>" in this element.
    Note: HTTP servers may alter or choose to ignore the suggested name.
    • content-type
    • content-transfer-encoding
    • content-id
    • other mime header information
    For more information about MIME headers and their syntax, see http://www.faqs.org/rfcs/rfc2045.html .

When the content type is specified as "text/*" (for example, "text/xml"), the attachment content is expected to be in either the textContent input element or the file name storing the attachment is expected to be in the fileName input element.

When the content type is anything other than "text/*", the attachment content is expected to be in either the binaryContent input element or the file name storing the attachment is expected to be in the fileName input element.

binaryContent | textContent | fileName

This element contains the mime attachment. The element can be one of the following:
  • binaryContent — content of the attachment when the attachment is binary data.
  • textContent — content of the attachment when the attachment is text data.
  • fileName — the file name of the attachment written to the disk.
Transport is HTTP. The following fields are available when the transport is SOAP over HTTP:
Element Description
host The host machine name or IP address to send the request to. For example, www.tibco.com.
port Port number on which the request was received.
endpointURI The address portion of the request. This is the portion before the question mark (?).
Note: If you want to change the endpointURI dynamically while invoking the service, set the Transport Properties accordingly.
Headers Headers from the request message.
  • accept: This field specifies media types that are acceptable for response messages for the incoming request. For example, text/*,text/html. Media types are described in the HTTP specification at w3.org.

    If no Accept header field is present, then it is assumed that the client accepts all media types.

  • accept-charset: This field specifies the character sets that are acceptable for response messages for the incoming request. For example, iso-8859-5, unicode-1-1. Character sets are described in the HTTP specification at w3.org.

    If no Accept-Charset header is present, then it is assumed that the client accepts any character set.

  • accept-encoding: This field specifies the content-coding values that are acceptable for response messages. For example, compress, gzip.

    For more information about this header field, see the HTTP specification at w3.org.

  • pragma: This field is used to include implementation-specific directives that might apply to the receiver.

    For more information about this field, see the HTTP specification at w3.org.

This field takes into account the encoding of the message body.

Dynamic Headers
The dynamic header is an additional header parameter to add runtime headers to the outgoing HTTP messages. The DynamicHeaders consists of the following information:
  • Name: the name of the header
  • Value: the value of the header
Transport is JMS. The following fields are available when the transport is SOAP over JMS:
Element Description
JMSTargetDestination Specifies the JMS destination(queue) name used to send messages.
JMSReplyDestination Specifies the JMS destination(queue) name used to send the response. The JMSReplyDestination specified has to be unique for every message. Set the JMSReplyDestination to a non-static variable such as Job-Id to use the same JMSReplyDestination multiple times.
JMSCorrelationID This ID is used to link a response message with its related request message. This property is usually set to the message ID of the message you are replying to, but any value can be used.
Note: Note: This is applicable only when JMSReplyDestination is configured with SOAP over JMS.
The JMSCorrelationID of the reply message is set as follows:
  • When the JMSCorrelationID field is configured with a unique value, the JMSCorrelationID property of the request message is set with the unique value. The same value is also set as the JMSCorrelationID of the corresponding response message.
  • When the JMSCorrelationID input element is not configured, the value of the message ID of the JMS Request message is set as the JMSCorrelationID property of the response message.
JMSPriority Specifies the priority of the message.
JMSExpiration Corresponds to JMSExpiration property that specifies how long the message can remain active (in seconds).
soapaction Specifies the soapaction header for the operation. It overrides SOAP Action value.