Compaq AA-Q88CE-TE Setting up Callout Servers, Example 2-4 Reconfiguration Using Extend Facility

Starting and Setting Up RTR

2.4 Changing a Facility

Example 2–4 Reconfiguration Using Extend Facility

% RTR

RTR> start rtr /node=(TR3,FE4) RTR> set environment/node= - 1

_RTR> (FE1,FE2,FE3,TR1,TR2,BE1,BE2,BE3,TR3,FE4)

RTR>	extend facility	funds_transfer -	2
_RTR> /router=TR3/frontend=(FE3,FE4) -
_RTR> /backend=(BE1,BE2,BE3)
RTR>	extend facility	funds_transfer -	3

_RTR> /router=TR1/frontend=FE4

1The set environment is used to send the following command to all nodes in the facility, including the new nodes.

2The extend facility defines the new router TR3 and the new frontend FE4. Because the new router is also connected to the existing frontend FE3, this node must also be specified as a frontend. The new router TR3 is told about all backends with the /backend qualifier. Note that the extend facility command has been used to create new definitions on TR3 and FE4, and extend the definitions on BE1, BE2 and BE3.

3The extend facility command is used to extend the definitions on TR1 and FE4 in order to give FE4 a second router link.

2.5Setting up Callout Servers

Callout servers are applications that receive a copy of every transaction passing through the node where the callout server is running.

Like any other server, callout servers have the ability to abort any transaction that they participate in. Callout servers are typically used to provide an additional security service in the network; transactions can be inspected by the callout server and aborted if they fail to meet any user-defined criteria. Callout servers can run on router or backend nodes, or both.

Assume that callout servers are to run on the router nodes (TR1 and TR2) in the example configuration shown in Figure 2–1. Example 2–5 shows the commands needed to set up callout servers on the routers.

Starting and Setting Up RTR 2–7