Chat now with support
Chat with Support

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

Remote Desktop

You cannot record FTR-A scripts using Remote Desktop.

Verify script playback

Verify script playback in the recorder on the agent machine, thereby taking the agent out of the process.

b
If running an FTR Advanced script, extract the CitraTest® script by right-clicking on the CitraTest instruction and choosing Export Instruction Data, then run the script in CitraTest.
3
Set the script to Run Visible (temporarily).
b
c
Click Modify the private properties for this agent link.
d
Click Edit.
e
Check the required scripts in the Force Script To... column.
f
Click Save Changes.
4
Watch the script playback. Set the Run Visible option to False. Since only one script can play visibly at a time, it is important during normal operation to set Run Visible to False in order to run multiple scripts in a timely manner.

Ensure users are logged out before running a script

In scripts where you need to log into systems, it is best to ensure that the user is logged out at the beginning of the script. By adding this step, your script runs successfully even if the previous script failed to log out the user. For example, in PeopleSoft the script should navigate to the https://.../?cmd=logout page instead of a https://.../signon.html page which will logout the current user and prompt for a new user login.

Run as a user

Edit the agent ASPs to run As User, using the same user that logged into the machine in Step b.

2
3
Click Modify the private properties for this agent link.
4
Set Play Script as User to True and enter the User Name, Password, and Domain information for the user that was logged into the machines where the script was recorded.
NOTE: The change takes effect after restarting the agent, only if the script path is valid on the agent machine. After setting the “Script Directory” property, the script files are moved under the %Script Directory%\Agent Name\scripts directory, and the results files are moved under the %Script Directory%\Agent Name\results directory.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating