This activity may be used to receive name-value pair data and file data received via HTTP using the multipart/form-data format. It may be used:
HTTP Inbound (Server) Processing in LANSA Composer
HTTP Outbound (Client) Processing in LANSA Composer
Upon successful completion, the multipart data is made available via the HTTP_RECEIVED_TYPES , HTTP_RECEIVED_NAMES and HTTP_RECEIVED_VALUES output parameters:
INPUT Parameters:
HTTP_HANDLE: Required
This parameter must specify the session handle value that identifies the HTTP session upon which this activity should operate. The session handle value is returned by the HTTP_BEGIN_INBOUND or HTTP_BEGIN_OUTBOUND activity.
OUTPUT Parameters:
HTTP_RECEIVED_COUNT:
Upon successful completion, this parameter will contain the count of the name-value pair data and file data received.
HTTP_RECEIVED_TYPES:
Upon successful completion, this parameter will contain the "types" of the items received. It is a variable list containing the number of entries identified by the HTTP_RECEIVED_COUNT parameter. Each entry will contain:
- the value 'FIELD' if the corresponding multipart item is a name-value pair
- the value 'FILE' if it represents file data. You must use the HTTP_MULTIPART_GET activity if you wish to receive the file content.
HTTP_RECEIVED_NAMES:
Upon successful completion, this parameter will contain the "names" for the name-value pairs or file items received. It is a variable list containing the number of entries identified by the HTTP_RECEIVED_COUNT parameter.
HTTP_RECEIVED_VALUES:
Upon successful completion, this parameter will contain the "values" for the name-value pair items received. It is a variable list containing the number of entries identified by the HTTP_RECEIVED_COUNT parameter.
(For those entries that represent multipart file data the value of the corresponding entry in this list is undefined.)