Versions Compared

Old Version 4

changes.mady.by.user user-eb51a

Saved on

compared with

New Version Current

changes.mady.by.user user-eb51a

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Most often, however, you may leave the default Automatic setting, which will result in the applicable HTTP activity setting an appropriate content type according to the file extension of the file being sent.  (This is achieved by a lookup on the file filetype.txt in the <system> directory of the server's JSM instance directory tree.)

Encoding

You may enter an encoding which will be used to convert the content to Unicode.

Content file directory

You may enter the local directory path which contains the content file.  You can click the prompt button to browse for a folder location on the LANSA Composer server.

NOTE: Although you can identify a specific content directory and file here as part of the HTTP configuration, it is more common to leave them blank and specify them dynamically on the parameters of the applicable HTTP activity in your Processing Sequence.

Content file name

You can enter the content file name. This file will be used as the payload of the HTTP transmission.

NOTE: Although you can identify a specific content directory and file here as part of the HTTP configuration, it is more common to leave them blank and specify them dynamically on the parameters of the applicable HTTP activity in your Processing Sequence.

Note

Note: 

  • A Test button can be used to check the validity of the parameters for Outbound HTTP Configuration.
  • The parameters tested are: Remote host, Proxy server, Secure protocol, SNI
host name
  • hostname, Authentication user and password, and Connection and Response timeout values, if applicable.
  • The HTTP remote host parameter length has increased to allow authentication methods to be added to the host URL.
  • There is also an increase in the URI to allow for longer queries.