This version of the documentation is not fully supported. However, the documentation is available for your convenience. You will not be able to leave comments.

See information on this topic in the latest version (11.3.01) or versions 11.0, 10.7, and 10.5.

After installing the App Visibility server components that are required for monitoring synthetic transactions and Installing a BMC Synthetic Transaction Execution Adapter Agent, you configure how to generate the synthetic transactions for monitoring from the App Visibility Manager.

You use the following features to set up the simulation of synthetic transactions:

  • Locations—Each synthetic TEA Agent is associated with a location, which is a logical group (such as by geographical location or application type), that is used for load balancing and high availability.

  • ScriptsFrom the TEA Agents, scripts run sequences of instructions that simulate user transactions. App Visibility comes with the six prerecorded scripts. You can use an external scripting tool to create more scripts.
  • Execution PlansAn Execution Plan is a wrapper for a script. Through an Execution Plan, you specify the configuration for the script (including custom attributes), locations on which the script runs, run schedules, and blackout periods. Every Execution Plan is associated with an application. You can modify or override some of the settings in the Execution Plan definition.

This section presents the following topics:

Related topics

Getting started with synthetic transaction monitoring

Synthetic transaction monitoring

Monitoring synthetic transactions to predict application health

Using scripts to simulate end-user transactions

Was this page helpful? Yes No Submitting... Thank you
© Copyright 2013-2016 BMC Software, Inc.
© Copyright 2013-2016 BladeLogic, Inc.
Legal notices