HTTP Listener startup configuration

An HTTP Listener routes HTTP requests from external clients to maps in the Launcher and returns a response to the external client. Use the Launcher Administration utility Options page and select Listeners to add, remove, and update HTTP Listeners.

HTTP Listener settings

Name
A unique name of up to 25 characters to represent a listener.
Mode
When enabled, the listener starts automatically when the Launcher starts. By default, the listener is disabled.
HTTP port
The port that the listener uses to communicate with external clients. The listener monitors the HTTP port for incoming HTTP requests and responds to the external client through the HTTP port. Each listener must use a unique HTTP port. If you configure multiple listeners to use the same HTTP port, only one listener starts when the Launcher starts. The default HTTP port is 5017.
Launcher port
The port that the listener uses to communicate with the Launcher. Each listener must use a unique Launcher port. If you configure multiple listeners to use the same Launcher port, only one listener starts when the Launcher starts. The default Launcher port is 5018.
HTTP certificate
Specifies the server certificate used for SSL communication with external HTTP clients on the client port. If you omit it, SSL communication between the HTTP Listener and external HTTP clients is disabled.
Launcher certificate
Specifies the server certificate used for SSL communication with HTTP adapters on the Launcher port. If you omit it, SSL communication between the HTTP Listener and maps is disabled.
Log level
The trace setting for the HTTP Listener. The Launcher creates a unique trace file name by appending the current date, timestamp, and computer host name to the HTTP Listener name (for example, lsnr_a_socket07-06-16-02-11-14-PM_myhostname.log). Logs are created in the installation directory on Windows systems and in the \bin directory on UNIX systems.
None
Tracing is not enabled for the HTTP Listener. This is the default setting.
Standard
Logs the HTTP Listener activity. The log file name is listenername_timestamp_hostname.log.
Verbose
Logs the HTTP Listener activity and socket activity. The log file name is listenername_socket_timestamp_hostname.log.
Audit
Enables or disables an audit log of Transformation Extender map executions and each adapter connection and external client connection to the listener. The audit log is in XML format that can be queried with XSLT transformations. The audit log schema is LHL-Audit.xsd, installed in the Transformation Extender installation directory on Windows systems or the /bin directory on UNIX systems. Auditing is disabled by default. There is one audit log per listener.