Filter
Top Products
Chapter 3. Implementation scenario: Standalone Proxies 99
Figure 3-2 RC Proxy Implementation
In this environment, we defined the machine tic01002 as RC Target Proxy and
the machine tic01005 as RC Controller Proxy. In our case, both of these are also
the Tivoli resources.
The RC Target Proxy has been defined as Parent Proxy, and the RC Controller
Proxy has been defined as Child Proxy. We use a unidirectional connection, and
we define the RC Target Proxy as the initiator.
3.2.2 Data flow description
In this section we describe the data flow in our network topology based on our
testing scenario. We also highlight the ports used for the communication
between each Remote Control component, preparing the base for 3.3.3, “Firewall
configuration table” on page 108.
Endpoint
Windows TS server
Hub TMR server
AIX 5.1 - tic01010
TMR Spoke
TMR Hub
Remote Control
Connections
Framework
Connections
Firewall
De-Militarized
Zone (DMZ)
Spoke TMR server
AIX 5.1 - tic01002
Endpoint Gateway
Windows tic01005
RC Controller Proxy
- child -
Endpoint
Windows tic01006
Remote Control
Controller
Endpoint Gateway
AIX 5.1 - tic01002
RC Target Proxy
- parent -
- unidirectional -
Endpoint
Windows tic01005
Target Endpoint
Endpoint
Windows tic01007
Target Endpoint