Launcher HTTP Listener overview

The HTTP Listener component of the Launcher provides secure, two-way communication between external clients and the Launcher. The HTTP Listener is included in the Design Studio installation. The HTTP Listener can automatically recognize an MTOM message and store the attachments in a user-designated location.

An external HTTP client can trigger a map in a Launcher system by sending a request to the Launcher HTTP Listener. Regardless of whether it runs successfully, the map returns a response through the HTTP Listener to the external HTTP client. If the map fails or the output card does not return a response to the client, the input card automatically returns a response.

The HTTP Listener executable name is httplsnr. This functionality supports the following features:

  • Allows you to configure HTTP Listeners in Launcher Administration.
    • Add a new HTTP Listener
    • Remove an existing HTTP Listener
    • Update an existing HTTP Listener configuration
  • Runs HTTP Listeners that are enabled during the start up of the Java Launcher.
    1. The Java Launcher spawns HTTP Listener processes.
    2. The HTTP Listener process listens for client requests based on user settings.
    3. The HTTP Listener provides status information to clients.
    4. The HTTP Listener allows clients to configure non-start up settings.
    5. The Java Launcher restarts HTTP Listener if they terminates abruptly.
  • Allows you to monitor the HTTP Listeners from Management Console.
    • Monitor only those HTTP Listeners that are of interest to you
    • Provide Summary, Status, and Configuration statistics
    • Provide a manual refresh for status statistics, in addition to the automatic refresh
  • Provides command line interface support for HTTP Listeners.
    • Define HTTP Listeners with Launcher Administration command line utility
    • List HTTP Listeners defined by the user
    • Export and import HTTP Listener definitions in XML format
      Note: The Java Launcher can start HTTP Listeners with Launcher Administration XML.
    • Report the status of the HTTP Listener using Java Launcher command line utility
    • List HTTP Listeners running under Java Launcher
  • Provides status and configuration information updates for clients through the Management Console and web browsers.
    • View status and configuration updates
    • Audit HTTP Listener activity
  • Provides command line execution.
    • Includes many command line options for easy configuration and fast startup
    • Provides monitoring, auditing, and tracing from the command line console
    • Registers HTTP Client requests quickly regardless of the volume of requests
  • Provides remote control access.
    • Handles updates and real-time monitoring from a browser on a remote machine
    • Refreshes the web browser automatically in custom intervals depending on the window visibility
  • Allows real-ime monitoring of activity.
    • Reports the total number of HTTP client requests and the type of Launcher response
    • Reports the average map execution times per HTTP Adapter watch
    • Tracks the total number of connections and averages the elapsed time for the establishment of sessions
    • Reports the names and sizes of the audit and trace files
    • Displays statistics on command line console, web browser, and Management Console
  • Auditing
    • Reports each HTTP Client request and Launcher response in a XML schema format
    • Logs individual map completion times
    • Tracks each connection type and the elapsed time for session establishment
    • Activates on-demand and can be periodically archived once auditing is disabled
  • Expanded Tracing
    • Provides unique names for the standard and verbose trace files
    • Tracks regular events in standard trace file and socket activity in verbose trace file
    • Activates on-demand and can be periodically archived once tracing is disabled
  • Enhanced Triggering
    • Provides 2-way communication between the HTTP Adapter Input Card and HTTP Listener for added functionality and fast response times
    • Allows configurable HTTP response codes and messages based on map return code
    • Enables boilerplate and customized HTTP data responses that can include runtime map information
    • Guarantees timely HTTP Responses upon map failure