GUIDELINES FOR SCRIPTING WITH RTE PROTOCOL IN
LOADRUNNER 8.1
Name Org/Group Role Date
Prepared by: Sandeep Gupta NBCU Performance Tester 11/9/2007
Reviewed by:
Approved by:
All document control issues pertaining to this document or for information about its
access and location please contact the following resource(s):
CONTACT INFORMATION
Name: Sandeep Gupta
Role: Automation tester
Org/Group: NBC Universal
Phone: *901-4023
E-mail [email protected]
REVISION HISTORY
Section/
Version # Date Description of Changes Author
Page #
1.0 11/9/2007 Initial Document Sandeep Gupta
Guidelines for Scripting with RTE Protocol Page 2 of 15 10/15/2008
Classification: GE Internal
.I Purpose
• RTE Vusers operate terminal emulators in order to load test client/server
systems.
• You record a terminal emulator session with VuGen to represent a true user's
actions. You can then enhance your recorded script with transaction and
synchronization functions.
.II Introduction of RTE Vusers
• An RTE Vuser types character input into a terminal emulator, submits the data
to a server, and then waits for the server to respond. For instance, suppose that
you have a server that maintains customer information for a maintenance
company. Every time a field service representative makes a repair, he accesses
the server database by modem using a terminal emulator. The service
representative accesses information about the customer and then records the
details of the repair that he performs.
• An RTE Vuser emulates the actions of a real user. Human users use terminals or
terminal emulators to operate application programs.
• In the RTE Vuser environment, a Vuser replaces the human. The Vuser operates
PowerTerm, a terminal emulator.
• PowerTerm works like a standard terminal emulator, supporting common
protocols such as IBM 3270 & 5250, VT100, and VT220.
.III Terminal Setup
• After you create a skeleton Vuser script, you record the terminal setup and
connection procedure into the script. VuGen uses the PowerTerm terminal
emulator when you record an RTE Vuser script.
Guidelines for Scripting with RTE Protocol Page 3 of 15 10/15/2008
Classification: GE Internal
• Start Recording. Once PowerTerm window appears, go to Terminal setup.
Guidelines for Scripting with RTE Protocol Page 4 of 15 10/15/2008
Classification: GE Internal
• After selecting the appropriate Terminal Type, go to Communication Connect.
Guidelines for Scripting with RTE Protocol Page 5 of 15 10/15/2008
Classification: GE Internal
.IVRecommended Recording Options
Guidelines for Scripting with RTE Protocol Page 6 of 15 10/15/2008
Classification: GE Internal
Guidelines for Scripting with RTE Protocol Page 7 of 15 10/15/2008
Classification: GE Internal
.V Recommended Run Time Settings
Guidelines for Scripting with RTE Protocol Page 8 of 15 10/15/2008
Classification: GE Internal
Guidelines for Scripting with RTE Protocol Page 9 of 15 10/15/2008
Classification: GE Internal
Guidelines for Scripting with RTE Protocol Page 10 of 15 10/15/2008
Classification: GE Internal
Guidelines for Scripting with RTE Protocol Page 11 of 15 10/15/2008
Classification: GE Internal
Guidelines for Scripting with RTE Protocol Page 12 of 15 10/15/2008
Classification: GE Internal
.VI Running the script in Controller
• Before running the script in controller, you need to ensure following settings.
Guidelines for Scripting with RTE Protocol Page 13 of 15 10/15/2008
Classification: GE Internal
• ALLOW_RTE should be set to 1 in the file: C:\WINNT\wlrun7.hst
Guidelines for Scripting with RTE Protocol Page 14 of 15 10/15/2008
Classification: GE Internal
• For each Load Generator the RTE option should be Checked. Go to
Generators in the Design Tab of Controller. Select the Generator, click Details
and go to Vuser Limits tab.
Guidelines for Scripting with RTE Protocol Page 15 of 15 10/15/2008
Classification: GE Internal