Implementing Mercury J2EE Diagnostics with LoadRunner!

You should have the following with you prior the entire setup. If you are still unsure of the different components in a Mercury J2EE Diagnostics setup, I recommend you to revisit the article, “What’s Diagnostics?”, to gain a better understanding better before proceeding:

1. Mercury Diagnostics Server Installation Disc
2. Mercury Diagnostics J2EE Probe Installation Disc
3. Mercury LoadRunner Installation Disc (prior to LR 9.0, the AddIn is found on the Additional Feature Disk).
4. J2EE Diagnostics Module license for LoadRunner
5. Mercury Diagnostics license for Diagnostics Server
6. Mercury Diagnostics Server and Probe Installation and Configuration Documentation

What you need to know in advance:

1. The JRE information of the Application Server.
2. The location of the application startup script (not the WebLogic server startup script).

We will use the term Profiler and Probe interchangeably for the purpose of this article. In the setup, I’m using the following:

1. Mercury Diagnostics Server 6.5
2. Mercury Diagnostics Probe 6.5
3. Mercury LoadRunner 8.1 FP4
4. BEA Weblogic 8.1 SP5
5. BEA sample Application Server – Avitek TM Medical Records
6. Sun JRE 1.4.2_08
7. TCP 2006 opened for two-way communication from LoadRunner Controller machine to Diagnostics Server machine
8. TCP 2612 opened for two-way communication from Diagnostics Server machine to Application Server machine
9. TCP 35000 opened locally on Application Server machine.

Read the rest of this entry »

What’s Diagnostics?

The HP Diagnostics Software is a standalone software of its own that is fully functional by itself. It is designed to profile J2EE, .NET or ERP/CRM application, by capturing duration at the module level, displaying chain of calls, monitoring heap size and garbage collection. Of course, these are some things that you may be interested in J2EE from the overview level and Diagnostics have more to offer than the mentioned. Read the rest of this entry »