HTTP Configuration / HTTP Host
Parent topic: HTTP Host

HTTP Host: HTTP Tab

The product uses the information you provide in the General and HTTP to build HTTP URLs when an action is run. 

HTTP/HTTPs
For HTTPs servers only.
Possible values: HTTP or HTTPs - If the server requires Secure Socket Layer (SSL), select HTTPs.  .
Check certificate server name
Only available if you select HTTPs. Verifies that the server name in the received SSL server certificate matches the server name actually connected to.
Method
Select a method for each command supported by the server. See HTTP and HTTP/s Hosts.
  • The server might not require CONNECT (login) because:
    • The server may not need to identify the client, or
    • Instead, the other commands may have parameters that identify the client, or
    • Over SSL, the server may make use of client certificates to identify the client.
  • The server must at least support PUT and/or GET.
  • If the server supports GET, it usually will support DIR; otherwise it is difficult to get files without first knowing which files to get.
  • The server might support CONFIRM or DELETE (usually not both).
  • The server might support REQUEUE.
If the DIR command is supported by an HTTP POST method, information concerning how to parse the directory listing returned by the server is required.  This information is potentially used by GET or CONFIRM or DELETE commands to extract the available file "identifiers" one-by-one from the directory listing.
  • Line delimiter* - set of one or more characters that marks the end of a line in the directory
  • Header lines - number of header lines to be ignored at the beginning of the directory.
  • Field delimiter* - set of one or more characters that separates fields in a line
  • File identified - location in the line of the available file "identifier"
    • at position - the file id always starts at this column position (first column in line is 1)
    • by tag - the file id always follows this set of one or more characters
    • at field # - the file id is always this field # (first field in line is 1)

* Special escape sequences can be used to identify certain characters:

  • \s - space character
  • \t - tab character
  • \n - newline character
  • \r - carriage return character
  • \\ - slash character
Path
Supply the server Path for each of the commands.  Depending on the server implementation and the methods used, some or all the paths might be the same or some or all might be different.
Parameters
Headers
Specify required and optional Parameters and Headers for each of the commands.
Add custom parameters and additional headers as needed. The values for these will be available on the receiving side either through the properties passed to the ILexiComIncoming Java API or by accessing ISessionScript.getTrigger() in a JavaScript action scheduled for a new file arrives event.
If the Content-type is multipart/form-data, any configured headers will become form-data parts.
Rule Syntax Example
If the parameter/header has one static value.  If a parameter value includes an ampersand (&) or a vertical bar (|) or if a header value includes a comma (,) or a vertical bar (|), precede with a backslash (\& or \, or \|). name=value key=1
If the parameter/header contains a macro variable, it must be enclosed within two percent signs (e.g., "%index%").  See Using macro variables (Destination File context) for further details on macro usage.  Note that "macros" should not be confused with "keywords" (e.g., "%dir) that are also supported within the parameter/header values. name=value key=MY_NAME_%index%_%date%
If the parameter/header can have one or more possible values, separate with vertical bars (|).  To include a description with a possible value, separate the value and description with two percent signs (%%). name=|value1|...| type=|EDI|X12|
If the parameter/header can have unknown values name= user=
If the parameter/header value, when entered, should be masked, precede with an asterisk (*) *name= *psw=
If the parameter/header is optional, enclose with brackets ([...])

[name=value]

[name=|value1|...|]

[name=]

[*name=]

 [type=|EDI|X12|]
If the parameter/header should be sent to the server even when a value has not been entered, precede it with a plus sign (+) and enclose with brackets ([…]) [+name=] [+value=]
If the parameter is not a name=value pair but just a value, include the = before the value =value =true
If more than one parameter, separate with ampersands (&) name=value&name=value user=&*pswd=
If more than one header, separate with commas (,) name=value,name=value recvr=%tp,type=|EDI|X12|
If the parameter/header value can potentially be filled in via a  trading partner branch (LexiCom) or the Trading Partner table (VLTrader and Harmony), use the keyword %tp name=%tp recvr=%tp
If the parameter/header value is the contents of the source file being transferred, use the keyword %file name=%file file=%file
If the parameter/header value is the name of the source file being transferred, use the keyword %file.name name=%file.name filename=%file.name
If the parameter/header value is the extension of the source file being transferred, use the keyword %file.extension name=%file.extension filetype=%file.extension
If the parameter/header value can potentially be filled in from the results of a DIR command (one-by-one), use the keyword %dir name=%dir filename=%dir
If the parameter/header value should include a uniquely generated message identifier, use the keyword %messageID. name=%messageID id=%messageID
If the parameter/header value should always be sent to the server with no value, use the keyword %empty. name=%empty attribute=%empty
Parent topic: HTTP Host
© 2018 Cleo. All rights reserved.