HP Diagnostics has agents for Java, .Net, and Python. The Java and Python agents support multiple operating systems, for which there are separate installers available. In the following example we will install the Java agent on Windows using Oracle WebLogic.
Step 1: Accept license agreement
Be prepared to hit the “enter” key many times if you are installing using the command-line installer
Step 2: Choose Installation Directory
After this point, the Setup Module will automatically load, enabling configuration of the agent. If you are installing the agent from the command-line, you will need to navigate to the <installation directory>/bin directory and manually launch the setupModule script for your platform.
Step 3: Choose Configuration Options
Profiler Mode: The Agent can be run in a stand-alone configuration (no integration with the Commander), free of charge.
AD License: Use this if you intend to only integrate the Commander with LoadRunner or Performance Center
AM License: The Diagnostics Agent is also used as a data collector for HP TransactionVision. Diagnostics can also be deployed in an HP SaaS configuration. If you are installing Diagnostics in your environment and are not using TransactionVision, then select only the “Diagnostics” option.
Step 4: Enter an Agent Name and Agent Group
This step is important, as the names used here will appear in the Diagnostics Commander interface. Agent Group is used where you have multiple agents all performing a similar task, examples: “Production,” “Application123,” or “Cluster456.” Both Agent Name and Agent Group will be used by default for any Agent instances executed on this host. By appending “%” to your agent name, a unique incrementing number will be appended.
Step 5: Agent Configuration
In this step we are configuring the Agent to send its data to the Mediator. This may or may not involve a proxy server, depending on your environment. In many cases, the Agent and Mediator will be on the same subnet (good idea), with firewall configuration so that the Mediator and Commander can connect.
Step 6: Complete Installation
We will run the JREInstumenter in the next step, so no need to run it in this step. If we were to select the checkbox in this step, the JREInstrumenter would run against the first JRE/JDK discovered on the system, which may or may not be the one used by our application. By manually executing it in the next step, we explicitly identify which JRE/JDK we intend to use.
Step 7: Proceed Using the JREInstrumenter
The JREInstrumenter is a separate application, accessible from the windows program group. If you are installing from the command-line, you will need to navigate to the <installation directory>/bin directory and manually launch the JREInstrumenter script for your platform.
Using the JREInstrumenter, we select the JRE/JDK being used by the application to be monitored.The entire output of the JREInstrumenter is a string parameter we will append to our application startup.
Is running the JREInstrumenter required? It depends on the version of your JRE/JDK and Agent. HP strongly recommends that the JREInstrumenter be run as they reserve the right to apply additional Agent initialization features.
Step 8: Modify application bootclasspath.
This step is application specific, but the summary is that you will append the parameter from the JREInstrumenter to the application bootclasspath for your application. In some cases, such as when using IBM WebSphere application server, you may be able to use a graphical user interface. For Oracle WebLogic, there is a startup script where you can append the parameter. This step may take several attempts to work.
Step 9: View the Probe
You will know the probe is functioning when you can view its user interface at http://<host>:35000. Default username and password are both “admin.”