지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight Transaction Recorder 5.6.13 - Recorder User Guide

Overview of Foglight synthetic monitoring Use the Foglight Transaction Recorder Create and upload Foglight Transaction Recorder scripts View Foglight Transaction Recorder results Settings How Do I... Appendix: Best practices Appendix: Troubleshoot the Foglight Transaction Recorder Appendix: API for FTR Timer Usage

Appendix: Best practices

This section provides best practices when using the Foglight Transaction Recorder. The following topics are provided:

•
FTR Advanced/CitraTest best practices
•
Run FTR scripts as a local administrator
•
Gather network statistics when using Windows Vista or a later version
•
Scale Foglight Transaction Player Agents

FTR Advanced/CitraTest best practices

CitraTest® is an effective and robust software used to script applications. The learning curve is relatively short. CitraTest can be mastered in a few hours using the following best practices:

1
Verify the Foglight environment
2
Create and Run scripts on the same machine
3
Captured images should be as small as possible
4
Manually create the CitraTest scripts
5
Use the AppStart function to start applications
6
Maximize applications after AppStart
7
Script launching and closing of the application
8
Create and test FTR scripts containing the CitraTest script
9
Use the Restore Desktop features of CitraTest and FTR

Verify the Foglight environment

Before deploying FTR scripts, it is advisable to ensure that the environment is correct by deploying and running a test script. To do this, create a simple FTR script, publish it, create an agent, and configure it to run the script in and set to run As User. The script can be as simple as navigating to Google or to a home page set to About:Blank. The goal is to ensure that the script runs and return results, thereby verifying the configuration.

Create and Run scripts on the same machine

To eliminate as many variables as possible, the creation and playback environments should be identical.

•
Agent Machine—The development machine should be configured as a Foglight agent machine, with the agent started and stopped as necessary for testing. The creation and deployment of the test should all be done on the agent machine which is separate from the Foglight Management Server.
•
Run as User—When configuring the agent properties, scripts should be set to run As User and the user specified should be the same as the user that was logged on during script development.
•
Remote Access—Another important step in keeping the creation and playback environments identical, is to not use remote access or terminal services. While these may seem to provide identical environments, there can be subtle differences that affect playback and cause problems that can be difficult to diagnose. If it is not possible to work directly on the development machine, a remote control program that controls the default desktop (as opposed to creating a second desktop environment) should be used. DameWare Mini Remote Control is easy and inexpensive. A free trial is available at http://www.dameware.com/products/dmrc/. If another remote control product is used, it is up to the user to ensure that the product does not alter the display properties of the system when connected or disconnected. If it does alter the display properties, a script that plays back properly when remotely controlled may not play back correctly when the remote connection terminates.

When using DameWare Mini Remote Control, configure the settings to ensure that the display is consistent.

Figure 62. Default Host properties dialog box

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택