Using scripts to simulate end-user transactions

TrueSight Synthetic Monitor uses prerecorded .ltz scripts to simulate end-user transactions, and BMC provides some basic scripts. You can create realistic and customizable scripts through an external scripting tool, and then upload the scripts directly from the scripting tool or through the TrueSight console. The scripts require a compatible execution module. For details about supported scripting environments, see TEA Agent system requirements.

This topic provides descriptions of the scripts that are provided by BMC and instructions for managing the scripts that you have available in Synthetic Monitor. For instructions about preparing scripts, see your Silk Performer documentation.


Related topics

Editing-an-application-s-synthetic-settings

Notes

  • When executing scripts, TEA agents require the same user privileges as a real user would. For example: if you would normally require administrator-level privileges to access the monitored application, the TEA agent requires the same level of privileges to run a script on that application.
  • Transaction names in custom scripts must be no longer than 40 characters.

The following topics are presented:

Provided scripts

The following scripts are provided out-of-the-box and cannot be deleted, replaced, or downloaded:

Script name

Description

FtpPinger.ltz

Checks the availability of an FTP server by connecting to it and retrieving the current directory of the server. The script requires the following parameters:

  • Host - Host that is monitored.
  • Port - FTP port. Default is 21.
  • User - User name for authentication on the server.
  • Password - Password for user validation on the server.
  • Timer Name - Name of the FTP ping timer.

LdapPinger.ltz

Checks the availability of an LDAP server by connecting to it and exchanging authentication information between the client and server. The script requires the following parameters:

  • Host - Host that is monitored.
  • Port - LDAP port (standard - 389, SSL - 636).
  • Use SSL - (Optional) Select if you want to use an SSL ping.
  • Timer Name - Name of the LDAP ping timer.

Pinger.ltz

Checks the availability of a specific host by sending it an Internet Control Message Protocol (ICMP) echo request via TCP/IP. The script requires the following parameters:

  • Host - Host that is monitored.
  • Ping Timeout - Timeout value for the ping in seconds.
  • Number of Pings - Number of pings to be sent.
  • Data Size - Size of the data package to be sent in bytes.
  • Timer Name - Name of the IMCP ping timer.

Pop3Pinger.ltz

Connects to a POP3 server to check its availability. The script requires the following parameters:

  • Host - Host that is monitored.
  • Port - POP3 port (standard - 110, SSL - 995).
  • Use SSL - (Optional) Select if you want to use an SSL ping.
  • Timer Name - Name of the POP3 ping timer.

SmtpPinger.ltz

Connects to an SMTP server to check its availability. The script requires the following parameters:

  • Host - Host that is monitored.
  • Port - SMTP port (standard - 25, SSL - 465).
  • Use SSL - (Optional) Select if you want to use an SSL ping.
  • Timer Name - Name of the SMTP ping timer.

URLChecker.ltz

Checks a URL by downloading its page and embedded objects and verifying the title and content. The only required parameter is URL. All other parameters are optional, depending on the verifications that you want to include. The script includes the following parameters:

  • URL - (Required) The URL being monitored.
  • HTTP Proxy host - Proxy host to URL if required.
  • HTTP Proxy port - Proxy port to URL if required.
  • Use HTTPS for proxy connection - Specify whether to use an HTTPS proxy connection or not.
  • Use HTTP 1.0 through proxy connections - Use HTTP 1.0 when connecting to Web sites by using a proxy server.
  • Some proxies have problems using HTTP 1.1. If you are experiencing difficulties, try selecting this parameter.
  • Bypass proxy server for local addresses - Select this to set browser-level functions to bypass proxies to hosts that do not contain a period in their names.
  • Do not use proxy server for - List of host names and IP addresses that you do not want routed through the proxy. Host names are separated by spaces. The list can include wildcards.
  • Verify if the title is - String to be used for title verification. An accuracy error is raised if the title is not equal to this string (case insensitive).
  • Raise error if the title is - String to be used for title verification. An error is raised if the title contains this string.
  • Verify if the content contains - String to be used for content verification.
  • Raise error if the content contains - String to be used for content verification. An error is raised if the content contains this string.
  • Suppress domains - List of domains (separated by spaces) from which files may not be requested. Wildcards cannot be used. For example, if you enter mydomain.com company.com, all host names that include these strings are suppressed. This is useful for suppressing embedded objects.
  • Link Checking - Select to check all links on the monitored page.
  • Detailed Page Timers - Select to enable detailed page timers (for example, Send, Recv, and Server Busy times). Results for detailed page timers are returned with the results for custom timers.

Note

Script attributes of scripts provided by BMC do not support non-English characters.

To view the list of available scripts

  1. From the navigation pane in the TrueSight console, and then click Configuration > Synthetic Scripts.
  2. To modify the list, click the relevant column heading to sort the list based on a specific column.
    To sort in reverse order, click the column heading again.

To upload custom scripts

  1. From the navigation pane in the TrueSight console, and then click Configuration > Synthetic Scripts.
  2. Next to the Synthetic Scripts page title, click the action menu and select Add Scripts.
  3. Browse and select one or more script (.ltz) files.

  4. Click Upload.

    Notes

    • Custom scripts are displayed on the list with the user name of the user who uploaded the scripts. Scripts that are provided out of the box are displayed with System indicated for the user.
    • The Version number displayed for the scripts is taken from the Revision field in the Silk Performer project. (For scripts created in older versions of Silk Performer, the Version number is taken from the {{code language="none"}}
      <ProjectVersion
      {{/code}}      > field in the .ltp file of the Silk Performer project package.)

To download a script

  1. From the navigation pane in the TrueSight console, and then click Configuration > Synthetic Scripts.
  2. From the action menu of the specific script, select Download Script.
    Download script.png 

  3. The script is downloaded to the download location defined in your browser.

    Note

    You cannot download default scripts that are delivered with App Visibility.

To delete scripts from the list

Note

 You cannot delete default scripts that are delivered with App Visibility. 

  1. From the navigation pane in the TrueSight console, and then click Configuration > Synthetic Scripts.
  2. Perform one of the following actions:
    • To delete one script, from the action menu of the specific script, select Delete Script.
    • To delete multiple scripts:
      1. Select the checkboxes for the scripts you want to delete.
      2. From the action menu on the column heading row, select Delete Selected.
  3. Click Yes in the confirmation message.

To replace a script

  1. From the navigation pane in the TrueSight console, then click Configuration > Synthetic Scripts.
  2. From the action menu of the specific script, select Replace Script.

  3. Click the Browse button and select the replacement script file.

    Notes

    • The replacement script must have the same name as the original script.
    • Existing attributes must be of the same type as they were in the original script.
    • The Version number displayed for the scripts is taken from the Revision field in the Silk Performer project. (For scripts created in older versions of Silk Performer, the Version number is taken from the {{code language="none"}}
      <ProjectVersion
      {{/code}}      > field in the .ltp file of the Silk Performer project package.)
  4. Click Replace.


 

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