Input

For more information about mapping and transforming input data, see TIBCO ActiveMatrix BusinessWorks™ Process Design.

The input for the activity is the following.

Input Item

Datatype

Description

binaryContent

binary

The binary content of the response to the request.

asciiContent

string

The ASCII content of the response to the request.

Headers

complex

The fields of the header specified on the Input Headers tab. For more information about these items, see the description of the Input Headers tab.

Note: Only the first Send HTTP Response activity in a process definition can set the Headers element. If your process definition contains multiple Send HTTP Response activities, the headers are set by the first activity and this element is ignored for all subsequent activities.

DynamicHeaders

complex

The dynamic header is an additional header parameter to add runtime headers to the Outgoing Http Messages. This element is specified in the Input tab. Dynamic header consists of the following information:

  • Name — name of the header.

  • Value — value of the header.

Consider the following overriding conditions:

  • Overrides the value of the HeaderName with the value found in DynamicHeaders if it is a non-repeating header. If more than one occurrence of this header is found under DynamicHeaders, it throws the following exception:

    "The header [ headerName ] is defined as non-Repeating Header in Input Headers. This header cannot have multiple occurences in DynamicHeaders."

  • If it is repeating element, add the respective name value pairs under dynamic headers, which can be added to the existing list maintained for this element.

  • For a repeating element, if the new header name is not found under Headers section declared via TIBCO Designer, following is added into the HTTP Headers.

    • Shows only one value, if found once in DynamicHeaders.

    • Shows array of values, if found repeating in DynamicHeaders.

mimeEnvelope
Element

complex

This element contains the message attachments. This element contains a repeating element named mimePart that contains each mime attachment.

mimeHeaders

complex

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.

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

choice

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.