Depends; In order to answer the "depends", we need to understand some basics of JMS and its relation with LoadRunner. First, JMS can be implemented in two ways: (a) via HTTP/XML or (b) via RMI-Java. Going back to the fundamentals of LoadRunner on the article for protocols, "Which protocol to use?", its essential to know what's the communication mechanism in order to select the protocol from LoadRunner. A more detailed description on the different implementations can be found in "JMS over XML-RPC with HTTP protocol" from the TheServerSide.com.

When JMS is implemented via HTTP/XML, it's simple here with the typical record and replay of the HTTP protocol. However, be aware that the asynchronous natural of messaging technology still applies. (LoadRunner have "partial" support on asynchronous application, in my humble opinion not really an accurate measure of the JMS load test). Therefore, if you are recording via HTTP protocol, our suggestion is to understand the interval that the message is being sent to the server and emulate it as lr_think_time in the script. When recording the application, you will be able to see the XML tags within the web_custom_request similar to Web Services.

If it's implemented via RMI-Java, you will have to record using Java Record and Replay Vuser and this required understanding of the classes that communicates from the client to the server. The developer will be required to be involved in the recording as he/she can provide advise on the classes used. Furthermore, JMS implementation on RMI-Java requires a license for Java Record and Replay Vuser. Therefore, do take note of the availability of the licenses in your organization. If the JMS is implemented over T3 protocol in WebLogic, just have to take note that it's BEA proprietary version of the RMI-Java implementation. Some information of T3 can be found in the following links to help you gain understanding of it:

• FAQs: Server-Related Questions, What is the function of T3 in WebLogic Server? (BEA WebLogic Server 8.1 Documentation)
• Using WebLogic RMI with T3 Protocol (BEA WebLogic Server 9.1 Documentation)

Both of the above leads to the same "depends" as it is dependent on the underlying protocol used. To sum up, before the load test, conduct an assessment on the communication mechanism (HTTP/XML or RMI-Java). Use WinSock recording or WireShark Network Analyzer to determine the communication. In a HTTP implementation, we will see conventional HTTP headers and XML tags. While in RMI-Java implementation, it will be a load of binaries with identified variable values. Thereafter, proposed the appropriate recording solution to it.