Service Binding - Request Context

Using Request Context you can map data from the Request Message to the Get Context Activity used in the process.

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.

  • method: The method specified in the request. For example, GET and POST.
  • requestURI: The address portion of the request. This is the portion before the question mark (?).
  • httpversion: Version field of the HTTP request.
  • querystring: The query string portion of the request. This is the portion after the question mark (?).
  • header: The header of the HTTP request.
  • protocol: Can be either HTTP or HTTPS depending upon the protocol used by the request.
  • port: Port number on which the request was received.
  • remoteAddress: The IP address of the client that submitted the HTTP request.

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.

  • content-type: This field indicates the media type of the entity body sent to the receiver. For example, text/html; charset=ISO-8850-4.

    Media types are described in the HTTP specification at w3.org.

  • content-length: This field indicates the size of the entity body (in decimal number of OCTETs) sent to the receiver.
  • connection:Use this field to specify options required for this connection.

    For example, the close option specifies that you want the connection to be closed when the request is complete.

  • 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

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: 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: 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.