Overview

• The supported deployment models are described in the Install Guide under Chapter 2 Deployment Topologies.
• Web weights are explained in the Install Guide under Multi Data Center Deployments and Multinode Installation. The web weight specifies the routing and relative counts of the initial HTTP request from the Web Proxy to a Unified Node. The initial request could be a request such as a transaction, or for example a GET request.
• Transactions can be processed on any Active Unified Node - regardless of which Unified Node processed the initial HTTP request. The transaction log provides the detailed information in the fields shown below:
  • submitter_host_name: the hostname of the application node that scheduled the transaction.
  • processor_host_name: the hostname of the application node that processed the transaction (this value is set once the transaction is processed).
• Note that a sub-transaction can be processed on a different Unified Node than its immediate precedent in the hierarchy.
• We recommend that you use both Web Proxies. However, the use of only 1 Web Proxy is supported (and Web Proxy use is optional).
• To display the configured web weights, run the command web weight list at the CLI of each Web Proxy Node .
• The recommended web weight settings for the various deployment models are shown in the following sections.