Filter
Top Products
Chapter 1. Remote Control sessions overview 21
1.2.2 Session in a multi-TMR environment
In order to continue to master the Remote Control session processes, it is also
important to know in detail the whole data flow between the different elements of
IBM Tivoli Remote Control in a multi-TMR environment. In a HUB-Spoke
architecture, all managed resources should be placed in the Spoke TMR, and all
profiles dedicated for the management should be created in the HUB TMR. As
RC Tools are managed resources, we assume that they are created in the Spoke
TMR. We also assume that the Targets are all managed by the Spoke TMR.
However, in order to let the Tivoli Administrator manage the Spoke TMR’s
resources from the HUB TMR, the Controller has to be declared in the HUB
TMR. This is because the resources of one Spoke TMR should never be able to
directly access resources of another Spoke TMR; only the HUB TMR resources
could manage all others. Furthermore, some resources, such as Endpoints,
Policy Region, and RemoteControl, need to be exchanged between the HUB and
Spoke TMRs. For more information about resources exchange between TMRs,
refer to the
Tivoli Management Framework Planning for Deployment Guide
,
GC32-0803.
Data flow for a multi-TMR session
Figure 1-3 shows in detail how a Remote Control session is working in a
HUB-Spoke TMR environment without firewall restrictions.