[COVID-19 - TSSA Customers Read This First] Options and Recommendations for using the TrueSight Server Automation (TSSA) console when working remotely

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Server Automation


    COMPONENT:

    TrueSight User Experience


    APPLIES TO:

    All versions



    QUESTION:


    Introduction:

    Many companies have been impacted by the Covid-19 virus which has required employees to work from home.  

    TrueSight Server Automation (TSSA) is an on-premise solution. The vast majority of the TSSA infrastructure (Application Servers, Databases, Repeaters, NSH Proxies, Target Agents) resides on-premise in the customer's corporate environment.

    These components will be unaffected by whether the end user is working remotely (from home) or in the corporate office.

    The only TSSA components which may be affected by whether the end user is working remotely or from the office are the Client Tier components. 

    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?

    This article explains what the various TSSA Client Tier components are, makes recommendations for how to run them when working remotely and provides links to some other articles which may be useful should certain errors or performance issues be encountered.



    The TSSA Client Tier - Additional Details:

    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:

    https://docs.bmc.com/docs/tssa2002/truesight-server-automation-architecture-910749414.html

    https://docs.bmc.com/docs/tssa2002/client-tier-910749426.html


    ANSWER:


    Recommendations on running the TSSA Client Tier when working remotely:

    When working remotely, it is not recommended to run the Client Tier utilities from the remote location, over VPN, connecting to the TSSA Application Server/Middle Tier. located in the corporate office/data center.

    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 TSSA 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.
    ____________________________________________________________________________________________________________________________

    Many customers already follow this recommendation and have designated "Console Servers" to which the end users connect (via either RDP or Citrix) and run the TSSA Client Tier tools.

    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 Tier and the Application Server:

    https://docs.bmc.com/docs/tssa2002/truesight-server-automation-ports-910749889.html#TrueSightServerAutomationports-Clientports



    Links to Knowledge Articles which may be useful when the Client Tier is running remotely:

    Performance:

    000188541  This article makes a recommendation to reduce the amount of traffic which would flow from the remote Appserver to the console and thereby improve performance.
    000166981 This article discusses how to troubleshoot console performance issues should they occur

    Connectivity Errors:

    000135169  TSSA Console Login failure, "connection failed could not resolve <appserver>"
    000095298  Login to the TSSA Console fails with error "Your session credential does not contain a usable application server URL.  Cannot connect to "service.appsvc.bladelogic.blsess://<hostname>:9841"
    000055991  Error when attempting to login to TSSA Console -  "Could not connect to "service:authsvc.bladelogic:blauth://appserver:port"

     


    Article Number:

    000188523


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles