This activity may be used to receive a file via HTTP. It may be used:
- With an inbound HTTP session – that is one that was initiated using the HTTP_BEGIN_INBOUND activity. In that case, it receives the HTTP inbound request content into the specified file. For more information on inbound HTTP processing in LANSA Composer, refer to:
HTTP Inbound (Server) Processing in LANSA Composer
- With an outbound HTTP session – that is one that was initiated using the HTTP_BEGIN_OUTBOUND activity. In that case, it is used AFTER sending an HTTP request, to receive the HTTP response content into the specified file. For more information on outbound HTTP processing in LANSA Composer, refer to:
HTTP Outbound (Client) Processing in LANSA Composer
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.
HTTP_RECEIVE_INTO: Optional
This optional parameter specifies the path and file name of the file that is to receive the HTTP content.
If not specified, or if the special value *AUTO is specified, the activity will generate a path and file name to receive the content. The directory will be taken from the system setting HTTP inbound payload directory. The file name will be derived from a prefix plus a unique number plus .dat extension. The prefix is taken from the system setting HTTP inbound filename prefix.
OUTPUT Parameters:
HTTP_RECEIVED_INTO:
Upon successful completion, this parameter will contain the actual path and file name of the file that received the HTTP content.
If you specified the path and file name on the HTTP_RECEIVE_INTO parameter, then it will be the same.
If *AUTO was specified or assumed for the HTTP_RECEIVE_INTO parameter, then this parameter contains the actual (generated) path and file name used.