Qorus Integration Engine  3.0.4.p7
qhaorder: Qorus Order Proxy Server

Usage
qhaorder [options]

The qhaorder program acts as an order proxy server for Qorus; when the Qorus server process is down, qhaorder will accept and process omq.system.submit-data.[workflow].[version]() API calls directly; creating the order information in the database and returning a correctly-formatted answer. If the Qorus server process is up and running, then qhaorder will pass through all API calls directly to the Qorus server and return the answer.

qhaorder starts up an HTTP server with XML-RPC, JSON-RPC, and YAML-RPC protocol handlers, just like the Qorus HTTP server. It is configured by setting the following options in the options file under the qhaorder domain:

  • qhaorder.listeners: one or more port numbers or interface:port number combinations, for example:
    qhaorder.listeners: 9001,192.168.20.5:9009 
    The default is to listen on port 9001 on all interfaces
  • qhaorder.daemon-mode: True or False if qhaorder should start up and immediately fork in the background, for example:
    qhaorder.daemon-mode: true 
    The default is True
  • qhaorder.verbose: the log level for the proxy server; messages with a log level equal to or lower than this value will be logged, all other messages will be discarded, for example:
    qhaorder.verbose: 3 
    the default is 2 (equivalent to OMQ::LL_DETAIL_1)
See also
OMQ::qhaorder_option_hash for valid options and OMQ::qhaorder_defaults for default option values for qhaorder

Options Supported by qhaorder

Long Option Short Description
–log-level=ARG -l Sets the log level (more -l's = more info)
–url=ARG -u Set URL: "http://host:port"; at least host or port must be given; ex: "http://server1:8501/RPC2"; see UNIX Socket Support in URLs
–proxy-url=ARG -p Set the proxy URL: "http://host:port"; at least host or port must be given; ex: "http://proxy1:8080"; see UNIX Socket Support in URLs
–show-url -W Shows the default URL
–help -h Prints command help text