Load generator connection

Skip to first unread message

jala ramu

Dec 20, 2009, 1:46:46 AM12/20/09
to LR-Loa...@googlegroups.com

 My question is how to estabilish connection from the controller( which is out side the firewall)  to load generator load generator machine (load generator is placed remote location) in firewall ?

could you please help me.

chaitanya bhatt

Dec 20, 2009, 2:41:27 AM12/20/09
to lr-loa...@googlegroups.com
You will have to use MI listener tool from Start>Loadrunner>Advanced settings menu.
Configure your LoadGenerator agent from within the firewall and make sure you have created a MI listener username and password. Also, be wary of choosing the right connection type between the agent and controller.

Chaitanya M Bhatt
Website: http://www.performancecompetence.com

You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
For more options, visit this group at

James Pulley

Dec 20, 2009, 9:41:07 AM12/20/09
to lr-loa...@googlegroups.com
Have you answered the question of whether your application can scale with a simple network of known quality first before involving a large geographically dispersed network of a medium to high degree of complexity (and therefore likely to skew your timing results for your app test)
From: jala ramu <jalar...@gmail.com>
Date: Sun, 20 Dec 2009 12:16:46 +0530
Subject: Load generator connection

chaitanya bhatt

Dec 20, 2009, 10:46:49 AM12/20/09
to lr-loa...@googlegroups.com
I think the author of this thread has a situation where the controller is operated from outside the network domain of the AUT but the LoadGenerators are installed within the network of the AUT.

Chaitanya M Bhatt
Website: www.performancecompetence.com

James Pulley

Dec 20, 2009, 11:36:30 AM12/20/09
to lr-loa...@googlegroups.com
There are a couple of possibilities here
  1. A process issue.   The tester is including a lot of uncontrolled factors related to network complexity in their test in the road to testing an application.   They are going to fall into the trap of getting something like Network response +application response = Total Application Response (42 Seconds).   Please solve for either network or application component.   The trick is you cannot because you need to hold one as a constant in order to solve for the other.   This happens often under a couple of circumstances
    • immature performance testers attempting to shortcut an application test by testing across a large complex network.   With two unknowns it can be a crapshoot for which item needs to be tuned to improve performance and this often results in the most common experience in all of IT, the network group and the application owner sitting in a room and throwing darts at each other as the cause.  A deliberately small network test results to definitely assign blame.
    • Using a third party generator set external to the organization, such as hosted generators.   Solved by either VPN software or defining ports appropriate to allow communication from the controller to the load generator to transparently transit the firewall.   This can be locked down by both port number and source IP address range limiting the risk that someone else with a LoadRunner controller will take over your load generator.
  2. A third party provider is using a LoadRunner controller at site A.  They are attempting to test an application at site B.   This is problematic from a license perspective.  I have included provisions from the controlling HP documents below to see how this is problematic
Comparing third party to hosted load generators the more common situation is the third party and I would almost be willing to bet on that here its third party involvement, which becomes much more complex from an acceptable licensed used situation.  
From the July 1, 2009 edition of

ADDITIONAL LICENSE RESTRICTIONS For Application Lifecycle Management Software Plus Business Availability Center Software


“Third Party Use

” means as authorized in the Software Specific License Terms, Licensee may permit a Third Party to access and use the Software on Licensee’s behalf for the sole purpose of providing services to Licensee, provided that; (i) If Licensee has a Site License then a Third Party may use the Software only at Licensee’s site (ii) for geographically restricted licenses Licensee has purchased the required Area or Global license for use at Third Party’s Location,(iii) Licensee designates’ Third Party as Licensee’s designated personnel under HP’s support and maintenance services, (iv) Licensee indemnifies HP for the use of the Software by the Third Party. Third Party may not use the Software for their own internal business purposes, nor permit any other third party to access the Software(v) Licensee shall provide written notice to HP of the Third Party’s name and the address of Third Party’s Location and (vi) Upon the termination or expiration of Third Party’s services to Licensee, Licensee shall promptly instruct the Third Party to remove and return all Software in its possession to Licensee. Licensee shall promptly notify HP of such termination or expiration.

“Third Party Location” means a location leased or owned by the Third Party.


HP LoadRunner

The HP LoadRunner Controller and AUT must reside at the same Site, but the Virtual User Generator, Analysis and Load Generators may be installed anywhere. Remote Access to the Controller is limited to users who are regularly employed and located at the same Site as the Controller.. HP LoadRunner Controller & Monitors Software includes unlimited Virtual User Generator development licenses   which may not be used: (i) stand-alone; (ii) with other HP products; or (iii) with any other product without HP’s prior written consent. HP Diagnostics licensed for use with HP LoadRunner may only be used with a licensed HP LoadRunner Controller. The HP LoadRunner Controller includes a license for 500 HP SiteScope Points. HP SiteScope Software that is bundled as part of the functionality within  another HP Software product must be used only with the Software originally licensed, and cannot be used as a stand-alone product, or with other third party software or other HP Software without HP’s prior written consent. Third Party access and use is permitted in accordance with the Third Party Use. HP Software licensed for load testing or functional testing purposes may be used only for the testing (load or functional) function originally licensed. For example, the HP Functional Testing license provided with HP LoadRunner may be only used for testing-related activities and functions; the HP LoadRunner license may not be used for automating operational tasks such as backup, synchronization or migration of data in production environments. HP is not liable for any consequences and or damages resulting from Use of the software to perform any functions for which is was not originally licensed. The HP LoadRunner demonstration tutorial Software included with HP LoadRunner may be used only for used for demonstration purposes. HP LoadRunner GUI is licensed per Virtual User and includes a single HP Functional Testing Seat License. The HP Functional Testing Seat license for use with HP LoadRunner GUI Virtual User license is restricted (i) not to be used for functional testing and (ii) only to be Used in conjunction with HP LoadRunner for performance testing purposes and (iii) shall not be installed on virtualized operating systems such as VMware or Citrix.  The Virtual User licenses are grouped in bundles, which are collections of virtual users that support similar technologies, environments or protocols. Virtual User licenses are Used per each Virtual User type included in an individual Virtual User script. For example, a single protocol Virtual User script which includes the Web (HTTP/HTML) Virtual User type will Use a single license from the HP LoadRunner Web & Multimedia license bundle. A multi-protocol Virtual User script will Use one Virtual User license from the license bundle for each Virtual User type included in the Virtual User script. For example, a multi-protocol Virtual User script which includes both Web (HTTP/HTML) Virtual User type from the HP LoadRunner Web and Multimedia Bundle and the Web Services Virtual User type from the  HP LoadRunner SOA bundle will Use two licenses; one each from the two separate license bundles.


From: lr-loa...@googlegroups.com [mailto:lr-loa...@googlegroups.com] On Behalf Of chaitanya bhatt
Sent: Sunday, December 20, 2009 10:47 AM
To: lr-loa...@googlegroups.com
Subject: Re: Load generator connection

Reply all
Reply to author
0 new messages