Hi I havent worked specifically with WebSphere (WebLogic being my thing), but this really doesnt matter , its a web -application and the principles are the same.
You have to first note what your app does on the browser (you can use LiveHttpHeaders, Fiddler, HTTPWatch or tool of your choice). Then identify what parts are dynamic (if you do the same thing again in a new browser window, what changes?.) Then find out where in the previous http request this data is present and then modify JMeter test to add a post processor to extract this data out into a variable and then change the JMeter test to use this variable in the next step. You should also add assertions to each step so that you can quickly identify which pages are failing. And finally you can use View Results Tree Listener to compare what JMeter sends and receives with what the Browser sends and receives. If you have any internet facing website we can take a look ... regards deepak On Thu, Apr 22, 2010 at 7:05 PM, daviddavid <[email protected]> wrote: > > Thank you. > Did you test portal application use JMeter successfully? > My test case navigates about 10 portal page and makes data update. After I > start JMeter and sent requests, I checked the WebSphere log, always got > invalid security ID and the data never be updated. > I have no idea what kind of post process I should do. It seems some server > related response security stuff should be saved, I do not know what they > are > and how to do it. Would you give me detail example about it? > > Thank you very much. > > David > > > Deepak Shetty wrote: > > > > Shouldnt be any difference from any other web app . Dynamic links almost > > always need a regex post processor or an XPATH post processor. A link > > parser > > is probably not appropriate. Do you have a specific problem? > > > > regards > > deepak > > > > On Thu, Apr 22, 2010 at 1:38 PM, daviddavid <[email protected]> > > wrote: > > > >> > >> Hi there, > >> > >> Did you sovle your problem? I mean test websphere portal apps using > >> JMeter? > >> > >> Thanks, > >> David > >> > >> > >> Oetting, Jan (ext.MA Consileon) wrote: > >> > > >> > Hi, > >> > > >> > I am testing Jmeter with IBM Websphere Portal, and mainly to the > >> dynamic > >> > links, it is not enough to use the HTTP Proxy, > >> > Because I get internal state error. > >> > > >> > A workaround is to use a post-processor, grepping the form (or links, > >> or > >> > whatever else i require), but if use longer regular expressions they > >> are > >> > often not evaluted correctly, so i need to formulate more complicated > >> > short regExs, and to formulate regular expressions needs some minutes > >> > anyway for each link, > >> > > >> > So I was happy to detect there is a HTML Link Parser, that proposes to > >> > analyse the previous sample for forms and links and to allow to > address > >> > them. > >> > > >> > I don't really understand the usage of these component. > >> > > >> > What I implemented (not working) is the following: > >> > > >> > HTTP Sample (previous page) > >> > HTTP Sample (current Page) > >> > Path = .* > >> > ->HTML Link Parser) > >> > > >> > > >> > Obviously this is wrong, can anybody help me out? > >> > Are the forms and links are stored in special variables, that I can > >> > access? > >> > > >> > Kind Regards > >> > Jan > >> > > >> > > >> > > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://old.nabble.com/Working-with-dynamic-links-%28HTML-Link-Parser%29-%28Websphere-portal-6.0%29-tp22080335p28334354.html > >> Sent from the JMeter - User mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > > -- > View this message in context: > http://old.nabble.com/Working-with-dynamic-links-%28HTML-Link-Parser%29-%28Websphere-portal-6.0%29-tp22080335p28336629.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
