Filter
Top Products
Starting and Setting Up RTR
2.4 Changing a Facility
Example 2–3 Reconfiguration Using Delete and Create Facility
% rtr
RTR> stop rtr/node=FE3
1
RTR> delete facility funds_transfer/node=TR2
2
RTR> create facility funds_transfer/node=TR2 -
3
_RTR> /frontend=(FE1,FE2) -
_RTR> /router=TR2 )
RTR> delete facility funds_transfer/node=TR1
4
RTR> create facility funds_transfer/node=TR1 -
5
_RTR> /frontend=(FE1,FE2) -
_RTR> /router=TR1 )
1
RTR is stopped on node FE3, the node being excluded from the network.
In order to prevent transactions being interrupted or aborted, application
processes should be stopped in an orderly manner before issuing the ’stop rtr’
command. Alternatively, a
stop rtr /abort
command will force application
processes using RTR to exit, aborting or interrupting any outstanding
transactions.
2
The facility is deleted on node TR2. Any frontends that were connected to
TR2 will connect to the remaining router, node TR1.
3
The facility is created on node TR2, excluding node FE3 from the frontend
list. This facility has started when the start message appears in the RTR log.
4
The facility is deleted from node TR1. Frontends FE1 and FE2 now connect
to router TR2.
5
The new facility is created on node TR1, again excluding node FE3 from the
frontend list. The frontends now distribute their connections to the router
nodes TR1 and TR2 according to the load sharing algorithm. The system is
again fully operational.
In the example in Figure 2–1, assume that a new router node TR3 and new
frontend FE4 are being added to the facility funds_transfer. The extended
configuration is shown in Figure 2–2. This diagram shows all possible
connections. The frontend connects to only one router at a time.
Starting and Setting Up RTR 2–5