
54 IBM Tivoli Remote Control Across Firewalls
Tra cin g for  RC Proxy-TFSTThe methods used to start a session i n a Remote Control Proxy-TFST 
architecture are the same that are used to start a session in a non-secure 
environment. Refer to Example 1-1 on page 16 for a subset of an IBM Tivoli 
Management Framework odstat command output for a single-TMR architecture; 
and to Example 1-6 on page 25 and Exam ple 1-7 on page 25 for multi-TMR 
architecture.
In “Tracing for single-TMR session” on page16 and “Tracing for a multi-TMR 
session” on page 24, we provided the detail of the most important methods used 
to start a Remote Control session both in a single-TMR and multi-TMR 
architecture. As mentioned, the methods are almost the same to start a Remote 
Control session in a secure environment. Thus, we only provide in this section 
the main differences for the most important methods.
The Target request, managed by the remote_control method, remains the same 
in a secure environment. For more information about this method, refer to 
Example 1-2 on page 19 for a single-TMR architecture an d to Example 1-8 on 
page 28 for a multi-TMR architecture.
The Example 1-19 details the is_proxied_ep method started from either the 
TMR Server in a single-TMR architecture or from the Spoke TMR Server in a 
multi-TMR architecture. It refers to the following line in Example1-7 on page 25:
1380596993.12.522+#TMF_Endpoint::Endpoint# is_proxied_ep 
This method checks if the Target is behind an Endpoint Proxy/Gateway Proxy 
architecture. If  the result is true, Remote Control knows that an Endpoint Proxy 
must be used to contact the Target. We see that the result of this method is true; 
this means that the Target is an Endpoint connected to a Gateway Proxy.
Example 1-19   The is_proxied_ep method for an RC Proxy-TFST architecture
loc-oc 11620                        9
      Results: (encoded): 
             true 
Example 1-20 details the nd_start_target method started from either the TMR 
Server in a single-TMR architecture or from the Spoke TMR Ser ver in a 
multi-TMR architecture. It refers to the following line in Example1-7 on page 25:
1380596993.12.522+#TMF_Endpoint::Endpoint# nd_start_target 
This method is used to start the local Remote Control process on the Target. A 
return code of 0; this means that the session starts without error.