This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Server Automation
TrueSight User Experience
TrueSight Server Automation (TSSA) users typically access their Application Server environment via a thick client known as the TrueSight Server Automation Console or, sometimes referred to as, the RCP Client.
They may also use their Network Shell (NSH) client to access the Application Server environment via a command line using Network Shell Proxy.
Some environments may even allow direct NSH access to Target Servers without requiring an NSH Proxy.
Users may also use a command line interface (BLCLI) that provides application programming interface (API)-level access to the functionality available through the console.
Similarly, users may use one of the TSSA Webservices interfaces (SOAP, RESTful and REST API) to automate certain tasks.
Collectively, these are known as the TSSA "Client Tier" and are discussed in more detail here:
If users are required to work remotely, what is the recommended way for them to access their TSSA "Client Tier" to minimize complexity and maximize performance?
When working remotely, it is not recommended to run the Client Tier utilities mentioned above from the remote location, over a VPN, connecting to the TSSA Application Server/Middle Tier.
Doing so will likely result in slow performance, as the Appserver and Clients send traffic over and back and is also likely to encounter connectivity issues such as Connection Resets and Timeouts.
The Performance Recommendations section of the documentation makes the following recommendation which would apply to all the Client Tier clients/utilities and not just the RCP client:
Application Server and the RCP client
The Application Server and the RCP client (the TrueSight Server Automation Console) must be located on the same Local Area Network (LAN). Remote users can use the console through either RDP or Citrix from a remote computer to the computer where the console resides.
If the Client Tier must be run remotely as a short-term workaround, see the following documentation for the ports which must be opened between the client and the Application Server: