Filter
Top Products
Chapter 1. Remote Control sessions overview 37
Based on Figure 1-6, here we detail each step from the time the Tivoli
Administrator opens a Remote Control Tool until the connection is established
between the Controller and the Target using the Remote Control Proxies.
The legend used in Figure 1-6 is explained as follows:
Steps A, B,C, D, E, F, G, H and I are similar to a Remote Control session in
single-TMR environment without firewall restriction. Refer to “Data flow for
single-TMR session” on page 14 for detailed information about these steps.
The remaining step is different and defined as follows:
J Both sessions on the Target and on the Controller are now started.
At this step, the Controller needs to establish the link to control the
Target. The rc_def_proxy policy has been configured to force the
usage of the Remote Control Proxies and the Remote Control Server
has been informed of that on step E. The Remote Control server then
has informed the Controller (step I) to use the RC Target Proxy in
order to contact the Target. The Controller is able now to transfer the
connection request to the RC Target Proxy as it got its IP address.
When the RC Target Proxy receives the request containing the IP
address of the requested Target, it can start searching in the
rcproxy.route file for the RC Controller Proxy the Target is
connected to. In fact, this file contains a list of all distant Endpoints
and their assigned RC Controller Proxy and needs to be manually
customized. For more information about how to configure this file,
refer to 3.3.2, “Remote Control Proxy configuration” on page 104.
The RC Target Proxy then contacts the correspondent RC Controller
Proxy to forward the Target connection request. The RC Controller
Proxy uses the Target information stored in the first request to start a
session with the Target.
The Remote Control session is now established. It is important to
notice that once the session established, the Controller talks directly
with the Target, but it’s
not a peer-to-peer communication
(Controller-Target) anymore, as the communication flow must always
go through the Remote Control Proxies.
The Target is listening on port defined in the rc_def_ports policy.
On the Controller side, by default, the port is assigned by the
communication stack. However, these ports could be easily changed
by configuring the rc_def_ports Remote Control Policies. The RC
Target Proxy and the RC Controller Proxy are listening on the port
defined during the installation process. The port specified in the
rc_def_proxy policy must be the same as defined during the
installation process of the RC Target Proxy. The configuration of
these RC Proxies ports could be reviewed by editing the rcproxy.cfg