Configuring TRA for Routing a Pricing Compilation
Traffic Routing Agent (TRA) can be configured to route generic TCP traffic from a client to a server, such as when routing a pricing compilation to proccessing servers in sub-domains over HTTP.
In this configuration, clients such as the HTTP Price Controller REST service (http_price_controller_app) connect to TRA-RT/DR TCP Virtual Servers (VSs) one per sub-domain, and the TRA-RT/DR routes pricing data to the TRA-PROC of the active MATRIXX Engine's proccessing node.
The following sections show example TRA-RT/DR and TRA-PROC configurations for TCP routing in a MATRIXX deployment with 3 sub-domains. All IP addresses and port numbers in the examples are for illustration purposes only.
TRA-RT/DR Configuration
In this example, the TRA-RT/DR has been configured to have a TCP VS for each sub-domain. The TCP VS for sub-domain 1 has the following configuration (other sub-domains follow the same pattern):
- name — pricing-sd1
- vip — vip-ext
- protocol — tcp
- port — 7101
- downstream-port — 7100
- pool — sd1-engine-pool
The pool sd1-engine-pool has the following configuration (other sub-domains follow the same pattern):
- name — sd1-engine-pool
- monitor — cmi-cluster-active
- monitor-port — 4800
- balance-method — single-node
- Nodes
id=”1” name=”engine-1” address=”10.10.20.101”id=”2” name=”engine-2” address=”10.10.20.102”id=”3” name=”engine-3” address=”10.10.20.103”
TRA-PROC Configuration
The TRA-PROC requires a tcp base VS to serve as a proxy for the
pricing service:
- name — pricing
- vip — vip-ext
- protocol — tcp
- port — 7100
- pool — proc-pool-any
The pool proc-pool-any has the following configuration:
- name — proc-pool-any
- monitor — cmi-node-active-cluster-active
- monitor-port — 4800
- balance-method — single-node
- Nodes
id=”1” name=”node-1” address=”10.10.21.111”id=”2” name=”node-2” address=”10.10.21.112”id=”3” name=”node-3” address=”10.10.21.113”