[chrisplough]

Kristof,

I've seen a variety of tools used to test OTM, including Rational, Mercury and JMeter. JMeter was often the most successful, but also the hardest to configure.

This usually occurs because the Web Tool isn't handling the OTM sessions correctly. In addition to handling the session cookie that OTM's Tomcat instance hands out, it needs to handle the unique identifier that you're seeing generated in the URL. This is used by OTM to facilitate more granular session control and may (though I could be wrong) be used by the newer JavaScript and JSP-based UI enhancements.

I don't know the facilities for managing this in Rational - but you need to ensure this number is captured dynamically and included within the associated URLs for that particular web session -- or at the very least that Rational isn't ignoring them and replacing them with the numbers generated at the time it was recorded.

Thanks,
Chris