Reference Binding - Response Context

Response Context enables you to map data from the Set Context activity to the response message.

Data Source

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

The following table shows the response message entities:

Elements of Set Context/ Response Message Description
Transport Properties Headers of the response message.
  • allow: lists the set of methods supported by the resource identified by Request URI.
  • content-type: indicates the media type of the entity body for the outgoing message and the incoming response. Media types are described in the HTTP specification at w3.org. An example of the media type is text/html; charset=ISO-8850-4.
  • content-length: indicates the size of the entity body (in decimal number of OCTETs) of the response message.
  • content-encoding: used as a modifier to the content-type. When present, its value indicates what additional content encodings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document to be compressed without losing the identity of its underlying media type. For more information about this field, see HTTP specification at w3.org.
  • date: date and time when the response message was sent.
  • pragma: used to include implementation-specific directives that might apply to the receiver. For more information about this field, see HTTP specification at w3.org.
  • location: used to redirect the receiver to a location other than the Request-URI for completion of the request or for identification of a new resource.
Dynamic Headers The dynamic header is an additional header parameter to add run time headers to the outgoing HTTP messages. The Dynamic Headers consists of the following information:
  • Name
  • Value
Headers

The fields of the header specified on the Input Headers tab.

Undescribed Headers Undescribed headers of the response message.
mimeEnvelopeElement Information about the attachments that are present in the response message. Individual attachment information is populated under one mimepart element. All attachments are configured as SwA unbound attachments.
Note: If the attachment size increases the threshold value configured at the binding level, the file name of the serialized attachment is populated.
mimeHeader

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.

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

For content type 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

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.