---

Introduction: You can find a description of this phase in section Phase 1 (Introduction). See also section HTTP and Lobster_data.

---

Data is requested via a URL. The response has to be in text format.

Note: See also section File Names, File Patterns, Paths, System Constants and Variables.

(1) Here you can select a channel of type HTTP. Note: If possible, always use channels to centrally manage connection parameters. In addition to the increased clarity that also facilitates maintenance. If the connection parameters change, you only have to adjust the data in one place and you do not forget a profile.

(2) If (3) is an HTTPS URL, you can optionally assign a client certificate. To do this, you select one of the local certificates.

(3) The URL (with port) of the remote HTTP(S) server. Note: There is no URL encoding.

(4) If set, the DMZ server (if available) will be used for sending the request instead of the internal Integration Server. Note: This also affects the OAuth token refresh if a channel (1) with configured OAuth was specified.

(5) You can set an optional timeout for the HTTP connection. Default: 90 seconds.

(6) If this checkbox is set, then HTTP status codes not equal to 2xx (success) do not cause the profile to terminate. This allows custom error handling. See also system variables MSG_CALL_VAR_HTTP_<name of header in uppercase letters>. Example: MSG_CALL_VAR_HTTP_STATUS_CODE .

(7) If you click this button, another dialogue opens, in which you can enter additional HTTP headers. You can use variables for the header names and the values. Syntax: @<Variable name>@. Note: You can use header Set-Cookie to write cookies. Note: See also section Additional IDs (in channel).

(8) Optionally, authentication data can be specified here. Variables are allowed. For Microsoft IIS with authentication by NTLM v1 or NTLM v2 see also section Windows Authentication at HTTP Server.

(9) This checkbox is only required when operating the profile as a web service. If set, additional button will appear below the data field. See section Web Services.

(10) The HTTP method, the MIME type (content type of the body) and the data (content of the body) of the HTTP request.

(11) and (12) You can insert multiparts or file attachments. Only HTTP methods POST, PUT and PATCH are supported, see (10). If a wrong method is used, method POST will automatically be set.

If the prefix file: is used in an entry in column Value/Path, e.g. file:./conf/data/communication_list.pdf, the file ./conf/data/communication_list.pdf is loaded at runtime and inserted as a multipart. You have to set checkbox Is file, the value of column File name replaces the name of the specified file and the MIME type is optional (default value application/octet-stream). Without the prefix, the content of the columns is inserted as a file attachment with UTF-8 encoding. In both cases, the key is arbitrary, but must be unique.

Note: The system property -Dhub.datawizard.multipart.browserMode=true enforces 'browser compatible mode'. If the property is not set or set to false, then 'strict' applies.

(13) The placeholder {--0:s#<template>--} for the last run can also be used here. Note: You can use MSG_CALL_ variables.