> -----Original Message----- > From: Trevor Johnson [mailto:[EMAIL PROTECTED] > Sent: 18 December 2003 13:31 > To: JMeter Users List > Subject: Re: Servlet Testing? > > > Hi Lee, > > Partial success at last! I can record some internal sites > now. I had to > modify > my browser's Internet Connection LAN settings to set the proxy name to > 'localhost' and the port number to the same as the port number in the > JMeter. > Is this correct? I wasn't sure what proxy name I was supposed to use.
The proxy server is run by JMeter, so you need to use the hostname and port that it is using. If it is running on the same node as the browser, you can use the hostname localhost. > > This solves half the problem I was having. I can record the hit on my > internal > sites entry page but that page contains an applet which call > a number of > servlets. > The first servlet performs the security check. JMeter > doesn't record any of > these > actions. > I may be wrong, but I suspect that is because the applet does not know that it should be using a proxy, and therefore does not make its requests via the JMeter proxy. The JMeter recording facility relies on the client using JMeter as its proxy - it does not intercept IP communications generally. If you could persuade the applet to use the JMeter proxy, and if it was using http, JMeter should be able to record the communications. Perhaps someone with more experience of applets can help here? > I guess to access this level of the site I need to use Java > Requests. Not necessarily - it depends what the applet is doing. If it is talking http, you should be able to use JMeter, once you know what the requests are. > I have one > of the programmers looking at setting up a class for me to use. > Might also be worth looking at TCP Sampler (and possibly the BeanShell Sampler, which would be good for prototyping). S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
