Launcher HTTP Listener
The Launcher HTTP Listener provides two-way communication between external HTTP clients and maps running under the Launcher. By default, the Launcher Server container starts the HTTP Listener during startup.
The HTTP Listener ensures that a REST request from an external HTTP client is received and processed by an ITX system flow that is watching for such an event. The Launcher Server container creates an HTTP Listener by name lshttplsnr. The HTTP Listener supports both HTTP and HTTPS communication protocols.
Certificates required to communicate securely among HTTP client, Listener and Launcher components are to be stored in a PKCS12 key store file. The default key store file wtx_keys.p12 is loaded from the /opt/runtime/config directory.
The Certificates that are used to communicate securely between HTTP client and HTTP Listener can be specified with the HTTP certificate environment variable. Similarly, HTTP Listener and Launcher communication can be secured with the Launcher certificate environment variable.
The key store file wtx_keys.p12 is loaded from /data/config volume under Kubernetes cluster environment like Red Hat OpenShift. The key stash file wtx_keys.sth is also loaded from /data/config volume when provided for the key store file.