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 |
Host |
string |
The HTTP host you want to connect to. Specifying a value for this input item overrides any value specified on the Configuration tab. |
Port |
integer |
The port number that the HTTP server uses for incoming requests. Specifying a value for this input item overrides any value specified on the Configuration tab. |
Method |
string |
The HTTP method to use for the request. All HTTP 1.1 methods are supported, but the CONNECT method is unnecessary because ActiveMatrix BusinessWorks automatically uses the connect method when connecting by way of a proxy server. If no method is specified in this element, the GET method is used by default. |
RequestURI |
string |
The address portion of the request. This is the portion of the URI before the question mark ( |
PostData |
string |
The message body of the HTTP request. Do not specify this element when the method of the request is GET. For more information about this input element, see Sending Data in the HTTP Request. |
QueryString |
string |
The query string portion of the request. This is the portion after the question mark ( For more information about this input element, see Sending Data in the HTTP Request. |
Timeout |
integer |
The amount of time (in milliseconds) to wait for a response from the HTTP server. |
Headers |
complex |
The header fields to send for the request. This element is specified on the Input Headers tab, and you can use this input item to supply values for the header when sending the request. |
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:
The following overriding conditions can be considered:
|
parameters |
complex |
Parameters for the incoming request. These parameters are configured in the Parameters field on the Configuration tab. This element is only available when there are items specified in the Parameters field. For more information about this input element, see Sending Data in the HTTP Request. |
mimeEnvelope |
complex |
This element contains the message attachments. This element contains a repeating element named mimePart that contains each mime attachment. Note: Only HTTP POST method can send messages with attachments.
|
mimeHeaders |
complex |
This element contains the mime header for each mimePart. Mime headers can contain the following 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:
|