This is a supplemental post to this one describing how to set up a VUser in LoadRunner to test OBIEE. It’s various notes that I made during the development but which aren’t directly part of the step-by-step tutorial. They’re not necessarily vital for recording scripts, but observations and explanations that should be helpful when working with LoadRunner and OBIEE. Validation using sawserver logs It’s no use running a load test if the load you think you’re applying isn’t actually being applied.

My two earlier posts (here and here) detail the difficulties I had with LoadRunner (now called HP Performance Center). After a bit of a break along with encouragement from knowing that it must be possible because it’s how Oracle generates their OBIEE benchmarks I’ve now got something working. I also got a useful doc from Oracle support which outlines pretty much what I’ve done here too. In essence what you do - and what the Metalink document 496417.

UPDATED: See a HOWTO for OBIEE and LoadRunner here: /2009/10/01/performance-testing-obiee-using-hp-performance-center-a.k.a.-loadrunner/ This is following on from my first post about OBIEE and LoadRunner, in which I failed dismally to get a simple session replaying. In a nutshell where I’d got to was using the “Web (Click and Script)” function which worked fine for logging in but when running a report resulted in an error on the rendered page. Digging around showed the error was from the javascript of the OBIEE front end.

UPDATED: See a HOWTO for OBIEE and LoadRunner here Introduction LoadRunner is a tool from HP (bought from Mercury) that can be used to simulate user activity. It supports a whole host of protocols but for OBIEE I’m obviously using the Web one. There are two flavours, “Web (Click and Script)” and “Web (HTTP/HTML)”. The latter simply shoves HTTP requests at the server, whereas “Click and Script” simulates mouse and keyboard entry and thus is more appropriate for this user-based application.