Chapter 1. Remote Control sessions overview 25
From Example 1-7, we could analyze that all methods needed to get information
from the HUB TMR are initiated on the Spoke TMR. Furthermore, all of these
methods will be found again in the HUB TMR trace file. Even if these methods
are initiated by the Spoke TMR, they are nevertheless managed by the HUB
TMR. In the Spoke TMR trace file (Example 1-7), we could also see that all
basis
Remote Control policies are loaded when the Tivoli Administrator opens the RC
Tool, and that all network related Remote Control policies are loaded each time a
Target request is started from a Controller. In addition to that, we could also
remark that the session is first started on the Target and then on the Controller
before the peer-to-peer connection between them is established.
In order to understand the information shown in the trace files, the Region IDs of
the HUB and Spoke TMRs in our environment are:
HUB TMR:
1380596993
Spoke TMR: 1519322503
Example 1-6 is the trace file from the HUB TMR Server.
Example 1-6 RC session trace from the HUB TMR in a multi-TMR environment
1380596993.1.536#TMF_LCF::EpMgr# get_endpoint_key_value
1380596993.1.536#TMF_LCF::EpMgr# get_endpoint_key_value
1380596993.1.179#TMF_Administrator::Configuration_GUI# _get_label
1380596993.1.631#TMF_UI::Extd_Desktop# connect
1380596993.7.522+#TMF_Endpoint::Endpoint# _get_label
1380596993.1.536#TMF_LCF::EpMgr# get_endpoint_key_value
1380596993.7.522+#TMF_Endpoint::Endpoint# nd_start_controller
1380596993.1.536#TMF_LCF::EpMgr# get_endpoint_key_value
Example 1-7 is the trace file from the Spoke TMR Server.
Example 1-7 RC session trace from the Spoke TMR in a multi-TMR environment
*******************************************************************************
Remote Control Tool is opened and RC Controller is checked.
*******************************************************************************
0.0.0 get_name_registry
1519322503.1.26 lookup
1519322503.1.26 lookup
1519322503.1.26 lookup
1519322503.1.26 lookup
1519322503.1.26 lookup
1519322503.1.4 lookup_id
1519322503.1.4##6@LCFData::ep_tnr_info_s describe
1519322503.1.26 lookup
1519322503.1.536#TMF_LCF::EpMgr# get_endpoint_key_value