Synthetic transaction configuration workflow

Gwen is a network administrator for PetRocks.com and she needs to plan, deploy, and configure synthetic transaction monitoring to check the performance when a user logs onto the website from a certain location. She needs to set up monitoring for the availability and accuracy of the web-based shopping cart application from different locations to see that the end-user experience is working according to the service-level agreement.

Gwen must perform the following tasks:

Plan Agent Groups and install the TEA Agent

Gwen must identify the the exact host computers on which to install the BMC Synthetic Transaction Execution Adapter (TEA) Agents. Each Agent is associated with an Agent Group, which is a logical group (such as by geographical location or application type), that is used for load balancing and high availability.

From the TEA Agents, synthetic scripts run sequences of instructions that simulate user transactions.

Understand the script

Gwen examines the provided URLChecker script, which checks the availability, accuracy, and response time of the URL by downloading its page and embedded objects, and verifying the title and content. The script is wrapped by an Execution Plan, which determines the Agent Group, script definitions, run frequency, and blackout periods.

Configure a Business Service

Before configuring the Execution Plan, though, Gwen defines a Business Service, named “PetRocks Online Services,” in the BMC Application Management Console. A Business Service groups several characteristics, providing a way to set up one general definition that can be applied to several scripts, which are wrapped in Execution Plans. Business Services also simplify later searches for details.

Configure an Execution Plan

In the BMC Application Management Console, Gwen defines one or more Execution Plans, which are associated with the Business Service. The Execution Plans inherit settings from the associated Business Service. Through an Execution Plan, Gwen defines an Execution Plan, named “PetRocks Dealer Portal,” where she provides values for the parameters in the URLChecker script. The Execution Plan runs scripts over specified Agent Groups, which are logical groupings of TEA Agents.

Configure monitoring features for synthetic transactions

Gwen performs the following configuration tasks:

When the script runs, results are displayed in the Real User Analyzer and notifications of any problems are sent to configured recipients.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*