Chapter 2. Implementation planning 73
2.2 Planning for IBM Tivoli Remote Control Proxy
As IBM Tivoli Remote Control Proxies require additional supporting applications,
such as the Tivoli Management Framework and, optionally, the Tivoli Firewall
Security Toolbox in an RC Proxy Non-Standalone environment, the entire
installation process, including Tivoli installation and firewall configuration phases,
is depicted in Figure 2-1 on page 74 and Figure 2-2 on page 75. However, in this
section, we do not discuss the installation process for each of the pre-requisite
application; instead we focus on the installation process for the IBM Tivoli
Remote Control Proxies.
Figure 2-1 shows the entire installation process, which includes the supporting
application and the required firewall configurations phases for an IBM Tivoli
Remote Control Proxy Standalone environment.
Note: A Relay could, at the same time, be a Parent of the RC Controller Proxy
and Child of the RC Target Proxy in our scenario. This means that the
communication between the Relay and the RC Target Proxy could be
unidirectional and bidirectional between the Relay and the RC Controller
Proxy. The tables provided in 2.1.3, “Network considerations” on page 61 can
help you to understand all of the scenarios.
If the communication between the Relay and the RC Target or Controller
Proxy is unidirectional, refer to “Unidirectional communication with Relay” on
page 65. If the communication between the Relay and the RC Controller or
Target Proxy is bidirectional, refer to “Bidirectional communication with Relay”
on page 70.