Run SAP GUI scripts from Controller
The following steps describe tips for running SAP GUI scripts in a LoadRunner Professional scenario.
LoadRunner Controller settings
When working with a LoadRunner Professional scenario, set the following values when running your script in a load test configuration:
Ramp-up. One by one (to insure proper logon) in the Scheduler.
Think time. Random think time in the runtime settings.
Agent running modes
You can run the LoadRunner Professional (or LoadRunner Enterprise) Remote Agent in Process mode or Service mode. To run the agent in Service mode, follow the instructions in
To check the current mode, move your mouse over the agent's icon in the Windows task bar area, and read the description. If the description reads Load Testing Agent Service, it is running as a service.
Run the remote agent as a process
The following steps describe how to restart the agent as a process.
Stop the agent. Right-click the LoadRunner Agent icon and select Close.
Run magentproc.exe, located in the launch_service\bin folder, under the LoadRunner Professional installation.
To make sure that the correct agent is launched the next time you start your machine, change the Start type of the Agent Service from Automatic to Manual. Then add a shortcut to magentproc.exe to the Windows Startup folder.
Terminal Sessions. Machines running SAP GUI Vusers may be limited in the number of Vusers that can run, due to the graphic resources available to that machine. To increase the number of Vusers per machine, open additional terminal server sessions on the Load Generator machines. Select Agent Configuration from Start > All Programs > <product_name> > Advanced Settings, and select the Enable Terminal Service option. You specify the number of terminal sessions in the Load generator machine properties. For more information, see
LoadRunner Terminal Services Manager in the LoadRunner Professional Help Center.
Note: When the LoadRunner Agent is running in a terminal session, and the terminal session's window is minimized, no snapshots will be captured on errors.