Monitoring-wise, because all of the request response activity is asynch in nature the concept of a response time collected by lr becomes a bit null and void. Fortunately the application has a full audit trail inside of its db that we use to pull stats at the end of the test
karim ibrahim <kal...@hotmail.com> wrote:
>
>Hello all ,
>I am involved in a new performance project for TIBCO application with the following details :
>Type of the application : Middleware Application (TIBCO BW, TIBCO EMS) .Protocol that the users desktop uses to communicate with the back-end servers : JMS and AS2 .
>I made an online search and below the information that i found :
>-
>http://www.loadrunnertnt.com/concepts/does-loadrunner-support-jms-recording/
>
>-
>http://j9tech.blogspot.com/2008/09/with-explosion-of-message-oriented.html
>
>-
>http://performancetestinginfo.blogspot.com/2009/12/simulating-soap-messages-via-jms-in.html
>
>
>Please let me know if any one had a previous experience with performance testing with TIBCO applications , Protocols that will be used or any useful information that can help me in planning for this project .
>
>Accept My Regards,
>Karim
>
>
>
>
>
>--
>You received this message because you are subscribed to the Google "LoadRunner" group.
>To post to this group, send email to LR-Loa...@googlegroups.com
>To unsubscribe from this group, send email to
>LR-LoadRunne...@googlegroups.com
>For more options, visit this group at
>http://groups.google.com/group/LR-LoadRunner?hl=en