TS Synthetic - TrueSight Synthetic TEA Agent and Transport Layer Security v1.2

Version 1
    Share This:

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


    TrueSight App Visibility Manager Server


    BMC Synthetic Transaction Execution Adapter


    BMC Synthetic Transaction Execution Adapter (TEA) Agent version 10.5.00 and newer AppVisibility Portal - All Versions Silk Performer 19.5 and newer


    Question 1) Can TrueSight Synthetic TEA Agent to application server communications be configured to use Transport Layer Security (TLS) v1.2 as opposed to SSL?
    Question 2) What is the default communications protocol between TrueSight Synthetic application components, and how to configure or adjust if this capability is available?



    The default communications protocol between TrueSight Synthetic application components is one of the following:
    and is selected on runtime during SSL handshake. Since priority is given to the highest version, both sides support the selected protocol (between TEA Agent and App Visibility Manager server) will be TLSv1.2.

    NOTE: TLS communication for the site being monitored by the Silk Performer script is different that above, it can be defined in the Portal what version of SSL/TLS will be sent to TEA Agent, however the TrueLog data is separated from TEA Agent data (metrics, timers, etc). If the monitored site involves TLS/SSL then the script might capture that data and put it in the TrueLog, the TEA Agent does not prevent any data from the TrueLog to come in, it is up to the customer to prevent the site that contains that data.

    For Silk Performer 19.5:
    Within Silk Performer 19.5 (base install), it was found that a connection could still take place over SSLv3, due to the method used for this connection.
    BMC has Silk Performer 19.5 HF 5 which will address this issue on our EPD site. It is highly recommend to install this patch to address not only this port, but another issue that was found with Silk Performer 19.5 where Scripts stop running on TEA Agent that are running as a process. See the below link to a technical bulletin that discusses this issue:



    Article Number:


    Article Type:


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