Page tree
Skip to end of metadata
Go to start of metadata

The following components make up TrueSight Synthetic Monitor with Silk Performer. The table provides a brief description of the components, and then the illustration shows how they connect to each other. 

For information about the possible deployment scenarios, see Deployment options for Operations Management.

The following table contains the primary components that compose TrueSight Synthetic Monitor:

Core components for TrueSight Operations Management productsRequired components that are necessary for all TrueSight Operations Management deployments
TrueSight App Visibility Manager componentsApp Visibility components that are necessary for all TrueSight Synthetic Monitor deployments
TrueSight Synthetic Monitor with Silk Performer componentsComponents that are unique to TrueSight Synthetic Monitor

Operations Management basic deployment with TrueSight App Visibility Manager and TrueSight Synthetic Monitor

Core components for TrueSight Operations Management products

 Click here to expand...

Product or componentFunction
Atrium Single Sign-On

For user and tenant management and for authentication to the TrueSight console.

Note: Atrium Single Sign-on can be installed on the same server with the TrueSight Presentation Server if necessary.

For information about installing Atrium Single Sign-On, see Installing BMC Atrium Single Sign-On 9.0 .

Presentation Server

The Presentation Server provides monitoring functions, role-based access control, solution administration, and configuration for TrueSight App Visibility Manager, and TrueSight Infrastructure Management.

For details about the installing the Presentation Server, see Installing the Presentation Server.

TrueSight App Visibility Manager components



App Visibility Server

The App Visibility Server comprises an App Visibility portal and one or more App Visibility collectors. For more details, see Installing the App Visibility server components.

  • App Visibility portal

The App Visibility portal manages App Visibility collectors. The App Visibility portal communicates with the associated App Visibility collectors to gather the application's synthetic transaction data to be sent to the Presentation Server.

  • App Visibility collector

The App Visibility collector receives data from one or more TEA Agents. The App Visibility collector stores the data received from the agents. Each App Visibility collector has its own database.

TrueSight Synthetic Monitor with Silk Performer components

TrueSight Synthetic Monitor enables synthetic transaction monitoring so that specialists can predict application health and user experience. Synthetic transaction monitoring enables you to manage your applications by executing complex business transactions and monitoring performance and functional behavior.


Silk Performer is not supported on native IPV6 systems.

Workaround: Use dual-stack.



Silk Performer for TrueSight Operations Management

Silk Performer is a utility that enables application specialists to record .ltz scripts that simulate user transactions.

The scripting utility also serves as an execution module to run scripts on the computer with the Synthetic Transaction Execution Adapter (TEA) Agent.

Either the full Silk Performer installation or the Silk Performer agent must be installed on every computer where the TEA Agent is installed.

Silk Performer agent for TrueSight Operations Management

Execution module to run scripts on the computer with the Synthetic Transaction Execution Adapter (TEA) Agent


 If you install Silk Performer for TrueSight Operations Management, it's not necessary to install the Silk Performer agent.

See Silk Performer Installation Guide for more details.

Synthetic Transaction Execution Adapter (TEA) Agent

The Synthetic TEA agent runs synthetic scripts and transfers the results to the App Visibility collector.

Multiple TEA Agents can be installed on the same computer.

For installation instructions, see Installing a Transaction Execution Adapter Agent.



  1. What will be the source of the Event and flow of the event from the source for synthetic monitoring Events?  As here in above diagram, it shows the evtns are generated from TEA Agents and forwarded to APP VIS Portal, but i cant see any cell on the same so curious to know abotu the lifecycle to the events from synthetic.

  2.  AVM Events are managed and persisted in the AVM server.

    If event destination is configured in the  AVM component configuration in TSPS then the AVM Portal will send a notification event to the configured cell.


    1)      External event manager cell

    2)      If TSIM is configured as component then should select the TSIM component as the event destination.  In this case, notification events will be sent to the TSIM cell.

    3) none

    Doc link:  #6 Under Custom Setting