Re: Advice - Testing When Controller Can\'t See Clients
Proper test procedure would dictate testing with the smallest network possible until the application acheives a "known good" status, then migrating load out across a wide area/complex network to observe the change in response time. This eliminates the all too common finger pointing exercise of "your app is the problem: your network is the problem" when slow response times crop up.
You are going to need to have your controller and generators in an environment where each can communicate to the other during the test.
So, you're using your copy of LoadRunner to test someone else's application. Hmmmm. Read your license agreement very carefully. One can get into a great amount of license trouble when usage crosses domains/sites/organizations.