HP Diagnostics 9.00, 9.01

The full Diagnostics documentation set was updated and is included with the product. The manuals
are also posted on the SSO documentation download site for this release. To check for recent updates or
to verify that you are using the most recent edition, visit the following URL:

http://h20230.www2.hp.com/selfsolve/manuals

This site requires that you register for an HP Passport and sign-in. To register for an HP Passport
ID, go to:

http://h20229.www2.hp.com/passport-registration.html

Or click the New users - please register link on the HP Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product support service.
Contact your HP sales representative for details.

To view files in PDF format (*.pdf), Adobe Reader must be installed on your system. To download
Adobe Reader, go to the following URL: www.adobe.com

Installation Overview

Diagnostics 9.02 contains a full replacement of the Diagnostics components but note that there are special
upgrade installation instructions you must follow. Please refer to the upgrade and patch installation
instructions provided in the HP Diagnostics Installation and Configuration Guide in Appendix G.

The upgrade installation instructions are also provided in a document available with each download zip
(Upgrade_Patch_Install_Instructions.pdf). These upgrade install instructions are a duplicate of
Appendix G, provided in each download zip as a convenience.

Installation Notes:

Diagnostics 9.02 probes are not compatible with 9.0/01 servers.

If a Diagnostics 9.01 installation is upgraded to a later versions and that installation is integrated with
BSM, then the customer may have to do the following:

On the BSM server, find the HPOvSecCS*.msi file that was used to originally install
HPOvSecCS (HPOvSecCS is the Certificate Server).

Execute ovc -stop.

Use the HPOvSecCS*.msi file to uninstall the Certificate Server.

Use the HPOvSecCS*.msi file to reinstall the Certificate Server.

Execute ovc -start.

Go to all systems that were granted certificates and perform the certificate request and grant steps
again (see the HP Diagnostics Installation and Configuration Guide chapter on BSM Integration).

Integration of Diagnostics 9.02 with BAC and BSM 9.01/9.00

Diagnostics 9.02 can be integrated with the following BAC/BSM versions:

Business Availability Center 8.0x

Business Service Management 9.00/9.01

Diagnostics 9.02 integration with BSM 9.01/9.00 requires the changes documented below.

Install the OMI_00005 patch on the BSM 9.01 Gateway Server(s) and Data Processing Server(s). You
can get this patch from the SSO patch site by selecting the Operations Manager i product and
downloading the OMI_00005 patch.

Important Note on Root Access Requirement

If Diagnostics will be integrated with BSM 9.0 or later, root access is required on the commanding server on
UNIX for installation of the OM Agent and IAPA components provided with Diagnostics.

Root access is also required to run the switch_ovo_agent.sh script used in setting up the BSM Event Channel
integration. If the Diagnostics commander is not run as root on UNIX, the registration of Diagnostics in
BSM Admin will fail with a permission denied error since it calls the switch_ovo_agent.sh script. After you
get this failure you must execute the script manually as root on the commander (see the Diagnostics
Installation and Configuration Guide for more information). It is important that the BSM Admin
Diagnostics registration step is done first and after that the script is executed.

What's New in 9.02

Diagnostics 9.02 has a number of defect fixes and a number of new features shown below. Note that the
defect tracking number shown (for example 35266) is generally prefixed with QCCR1I.

Platform Support Changes

As of Diagnostics 9.00 the .NET Agent requires .NET Framework 2.0 or later. If you must support .NET
Framework 1.1, use an earlier version of the .NET Agent (8.x) which will continue to be supported via
patches and is compatible with later Diagnostics Servers 9.x.

New Features

BSM's Run-time Service Model population of data has been enhanced to link database CI instances
populated by Diagnostics with business transactions so you can see the complete transaction picture.

Background: In versions prior to Diagnostics 9.02, only database CI instances are populated (SQL
Server & Oracle) for databases discovered by the collector. There is no link from a business transaction
to a database CI which results in an incomplete picture of the infrastructure the transaction runs on.

Benefits: Functionality

It is now possible to enable call profile collection for a specific amount of time and/or when certain
conditions are met.

Background: In prior version of Diagnostics, call profiles are collected to show the minimum time of a
server request, maximum time and average time. There was no method for enabling addition call profile
collection.

Description: On demand call profile collection rules can be based on various conditions and combinations
of conditions. For example:

When the latency value meets a condition (such as exceeds or falls below) based on a given value

When CPU usage meets a condition (such as exceeds or falls below) based on a given value

When the HTTP status meets a condition (such as equals or not equals) a given value

When the consumer ID equals, contains or matches a given value

By creating On Demand Call Profile rules, it is now possible to narrow in on the problem area and then
use the call profiles that were collected to further debug the performance or availability issue in your
application.

Benefits: Functionality

Enhanced ability to create custom dashboards.

Background: An effort is being made in every release to make Diagnostics easier to use. Past versions
have had good Dashboard type capabilities. 9.02 brings new ways to create a Dashboard. The new
dashboard can be used within Diagnostics.

Description: With 9.02, creating custom dashboards is made easier than in the past with more features.
A Dashboard view exposes only the graphs and hides all controls to maximize the amount of
information which can be placed on the screens. The new Dashboard features include:

Dashboards can be created from a snapshot, which creates a dashboard with fixed entity metric
pairs (cannot be applied to other entities).

With any view in the UI, there is an action to save the view as a dashboard. If the user selects
specific entities (vs. top N) then the dashboard is locked, otherwise it can be used to open on a
selected entity (Open in Custom view)

Benefits: Usability, Functionality

TIBCO BusinessWorks 5.9 and Active Matrix Service Bus (AMSB) 2.3 user's can see SOA Service
Topology, Server Request Topology and end-to-end latencies (with call profiler) for SOAP/HTTP and
SOAP/JMS web services in Diagnostics.

Background: TIBCO BusinessWorks and AMSB use multiple threads to handle individual server
requests. Previous versions of Diagnostics did not correlate these threads into a single server request,
treating them each as a separate, uncorrelated, server request.

Description: Diagnostics now correlates these threads into a single server request, providing the user
with the end-to-end latency, Call Profile and Server Request Topologies. In addition, the SOA Service
Topology is now correctly populated.

Benefits: Functionality

Can distinguish two or more .NET Application Domains (AppDomains) with the same name on the same
IIS server.

Background: It is common to have multiple virtual directories (AppDomains) with the same name (for
example "CallChain"). In previous versions of the .NET Agent the probe_config.xml extract to enable the
CallChain AppDomain looked like this:

<\appdomain>

The configuration format does not provide a way to distinguish the distinctly configured CallChain
applications in IIS. The result of this was that that you had to enable all (CallChain AppDomains) or
disable all. This is not a desirable level of control to enable/disable Web Applications. More so, the
probes instantiated by all the CallChain AppDomains were named exactly the same and so the server
requests from these applications got attributed to the single consolidated probe on the server. The probe
metrics were also averaged over completely independent instances which would be incorrect data
presented to the user.

Description: The primary purpose of this feature is to be able to distinguish two or more AppDomains on
the same IIS server which have the same name. This feature changes the format for ASP.NET (IIS)
AppDomain configuration format in the probe_config.xml file to enable distinguishing the AppDomains
by qualifying each with the IIS configuration path. The new configuration for three CallChain applications
would be as follows:

</appdomain>

</appdomain>

</appdomain>

The resultant probes are now distinguished using the IIS path and show up in the Enterprise UI
uniquely.

Benefits: Functionality, Usability

A new collector has been added that connects to and gathers metrics from VMware environments.

Description: Collects data from vSphere and vCenter servers and displays data in two new views:
VMware Hosts view and VMware Guests view. Sideways drills exist that allow you to jump between the
two views in context.

Benefits: Functionality

Added support for .NET REST style web services over http.

Description: In the .NET Agent WCF REST services are supported with a new keyword:

keyword = REST

This keyword is added to the default out-of-the-box WCF.points file and so enabled by default in new
installations.

REST services will follow the Web Service Model in Diagnostics and will show up as SOA service with
similar properties (Namespace, Servicename, Operations) as Web Services. The Binding or WsPort is not
relevant for REST services and hence omitted.

Benefits: Functionality

Can configure the processing of data from mediators in batches.

Background: The commander broadcasts a database export query to all mediators and collates the
results. This collation can use up a lot of memory on the commander. Consider 60 mediators and 3000
probes: If the database export task runs a query like /probegroup/probe, the commander will end up with
a result set from all 60 mediators for all 3000 probes before the results are exported to the database.

Description: This enhancement will allow the user to set the processing of mediators in batches (e.g. get
results for 10 mediators, export these results and process the next 10 mediators and so on). This
configuration can be found in the property servers-per-query in the etc/data-export-config.xml
configuration file.

Benefits: Performance

Defect Fixes

Server

59785 - Discovery 7d NodeDataQueries taking minutes to run and for discover BizTxn, the query is run
for each application.

Problem: Some discovery queries were taking too long - Discovery of business transactions was using too
many queries to the server.

Resolution: Discovery queries were optimized to run a lot faster.

60468 - SMTP events - alert stays open even when an all clear alert is received.

Problem: When an alert is triggered a notification is received, however, when the condition cleared out
there is no clear alert event, or an OK notification.

Resolution: A new alert option was introduced that allows the user to enable/disable sending of
SMTP/SNMP alerts when the state changes from red/yellow to green.

This option is enabled by default for all new alerts.

51729 - Server Install fails - Permission denied.

Problem: Server Install fails - Permission denied errors:

sh: /opt/HPDiagnostics/bin/runscript.sh: cannot open [Permission denied]

Resolution: This release does not support installing as non-root. With this fix a non-root install will
work as long as the event agent (a.k.a. opc agent or OMi agent) is not selected. When installing
Diagnostics and selecting integration with BSM, a non-root installer must not select the agent
installation. The OMi agent can be installed later, as root.

40372 - Server - can't find 'Throughput' metrics after the metrics data export to external database

Problem: After the metrics data was exported to an Oracle database, the 'Throughput' metrics are not
present in the export.

Resolution: The "latency" record has additional information in it which includes CPU total and count,
timeouts, exceptions and throughput (calculated). None of these additional metrics were exported.

Diagnostics 9.02 has added the following metrics in the category "latency":

total_cpu

exception_count

timeout_count

throughput

These metrics will be exported as if they were separate metrics/records. Since the min/max is not
tracked for these, min/max will be set to 0.

51315 - Data Export not exporting accurate 'min' & 'max' values for JDBC metrics

Problem: Data export of probe metrics to Oracle for metrics:

WebSphere6/EXPAND_PMI[*]/connectionPoolModule.UseTime = JDBC Use
Time|milliseconds|JDBC Connection Pools

results in the Min and Max values being identical and do not appear to reflect correct data.
Data Exporter should export: Average (for time Period), Min Value and Max value. .

Resolution: The minimum and maximum data exported does not currently allow for decimal places.
The server code has been enhanced to use double to preserve the data precision. The new
schema will use database columns of type float to preserve the precision.

If the customer upgrades to 9.02 Diagnostics and continues to use the existing database from a prior
version, then the columns can be modified using the following DDL. This may affect any of the
customer's data consumers.

Oracle:

ALTER TABLE RECORD MODIFY (

REC_COUNT NUMBER(38),

TOTAL FLOAT,

MINIMUM FLOAT,

MAXIMUM FLOAT)

SQL Server:

ALTER TABLE RECORD ALTER COLUMN REC_COUNT DECIMAL(19)

ALTER TABLE RECORD ALTER COLUMN TOTAL FLOAT

ALTER TABLE RECORD ALTER COLUMN MINIMUM FLOAT

ALTER TABLE RECORD ALTER COLUMN MAXIMUM FLOAT

52765 - The priority that the data retention policy has over purging is not clearly documented and
discussed in the Installation Guide

Problem: Despite having specified a particular purging threshold e.g.

persistence.purging.threshold = 5G

the actual disk storage used is exceeding this amount. In these circumstances, messages of the following
form may be found in the server.log:

yyyy-mm-dd hh:mm:ss,ms: WARNING archive : The archive size threshold (5368709120) has been
exceeded by 35455152128 bytes to honor minimum purging policies and data preservation. Try
increasing the persistence.purging.threshold property, deleting some Incidents, or adding additional
servers. (logged only once)

In some case the available disk storage space is exhausted.

The priority that the data retention policy has over purging is not clearly documented and discussed in
the Installation Guide

Resolution: Updated the Diagnostics Install Guide, Appendix E Diagnostics Data Management to discuss
the affect of data retention settings on the purging mechanism including adding the following:

If you find that disk space is being exhausted this does not mean that purging isn't working it may mean
that one of the following factors has affected the purging mechanism. For example if you have allocated
10GB of disk space on the server for Diagnostics but you see the archive at 20GB in danger of exhausting
disk space on the system, this could be possible for any of the following reasons:

Purging interval has not been reached yet. You can adjust to a shorter interval.

There are a large number of snapshots on the system that by design do not get purged.

The data retention settings may be requiring too much data be retained. You may need to adjust
data retention in order to save disk space.

56717 - Diagnostics fail to publish topology to ODB

Problem: Diagnostics fail to publish topology to ODB. The metrics for uCMDB Relay failed in
Diagnostics monitor page.

Resolution: The HTTPS communication link from Diagnostics to the uCMDB has been fixed.

Integrations

52206 - LoadRunner 11 Controller crashes after J2EE Diagnostics addin is configured on non-English
OS

Problem: When installing the Diagnostics LoadRunner Addin the following message box with error
appears and the Controller crashes:

"Runtime error. Program wlrun.exe. Abnormal program termination."

Resolution: An internal error occurred and has been corrected. The crash will no longer occur.

52144 - Admin->Diagnostics shows fields for Gateway and DPS when it used to show 2 Gateways --
add descriptive type to registrar components page

Problem: The Diagnostics 9 server refers to BAC core and center servers, but the BAC UI refers to
Gateway and DPS servers.

Resolution: The registrar pages use internal terms. To help clarify, the type column now shows
"BSM GW/Core" and "BSM DPS/Center".

Java Agent

59397 - SAP RFC instrumentation not working.

Problem: Instrumenting a WebLogic 10.3.1 that uses a (customized) version 2.1.10 of the SAP JCO
libraries to talk to SAP R3. Capturing JCO$Client.execute methods works (after changing the
signature wildcard in the point) and extracting the RFC call name from the arguments works. However,
the need is to trend the individual RFC calls, i.e. show them in the outbound calls view, report & alert on
them, etc. The default [RFC] point never gets hit.

Resolution: Added 2 instrumentation points subclassing the original main instrumentation point. These
2 points apply for the SAP JCO 2.1.10 (or later) and JCO 2.1.9 (or earlier).

58553 - Enable "class.name.replace=s s#\\$Proxy[0-9]+$#$Proxy#" by default to avoid symbol table
explosion.

Problem: Server generates hundreds of java_pidxx.hprof files taking up GBs of disk space from symbol
table explosion due to issue with Java probe.

Resolution: Enabled the class name replacement algorithm by default to avoid symbol table explosion.

59787 - Missing SQL Statements in Diagnostics 9.01 for Class OraclePreparedStatement ExecuteQuery
on Oracle WebLogic 11g ADF

Problem: A regression occurred starting with Diagnostics version 9.01. Some oracle.jdbc.* do not get
instrumented anymore.

The regression was a side effect of optimizing (i.e. reducing the ovehead of) our instrumentation where
some duplicate class parsing was eliminated after noticing that the agent visted some classes more than
once. Unfortunately, this caused the probe to miss some classes completely (WARN: No method
signatures found ...). This happens for classes in oracle.jdbc.* packages, because they were excluded from
"preprocessing".

Resolution: Removed oracle.jdbc.* classes from the prevent.class.preloading.list property.

59794 - SOAP/HTTP Nested outbound calls not recognized.

Problem: For SOAP/HTTP Nested outbound calls, the outbound calls view showed the HTTP method
instead of the SOAP Service operation. This is because, by default, the last outbound call is the one
reported.

Resolution: Code was updated to prioritize the SOAP Service operation as the outbound call when
followed by an HTTP outbound call.

51725 - Massive SEVERE errors in probe.log with IBM Java 1.4.2 64-bit

Problem: Multiple errors in probe.log (examples follow) and so the probe does not report any data:

2010-10-14 13:26:37,523 SEVERE capture.metrics [Metrics Collection] Unknown error collecting metrics
for Mercury System, initialized: true [Mercury System] ->
com/mercury/diagnostics/capture/jni/VmwareJNI.getHostTimestampUsecs()J
java.lang.UnsatisfiedLinkError:
com/mercury/diagnostics/capture/jni/VmwareJNI.getHostTimestampUsecs()J
at com.mercury.opal.util.VmwareTimer.getTimestamp(VmwareTimer.java:66)
at com.mercury.opal.util.Timestamp.timestamp(Timestamp.java:345)
at com.mercury.opal.util.TimerDriftMetric.doubleValue(TimerDriftMetric.java:57)
at com.mercury.opal.util.TimerDriftMetric.getValue(TimerDriftMetric.java:46)
at com.mercury.diagnostics.common.metrics.MetricCollector.collect(MetricCollector.java:156)
at com.mercury.diagnostics.capture.metrics.CollectorAgent.run(CollectorAgent.java:749)
at java.lang.Thread.run(Thread.java:770)

2010-10-14 13:26:43,065 SEVERE com.mercury.diagnostics.common.util.InfrequentEventScheduler
[shared InfrequentEventScheduler] While running rare event:
com.mercury.opal.util.Timestamp$1@404e404e
java.lang.UnsatisfiedLinkError:
com/mercury/diagnostics/capture/jni/VmwareJNI.getHostTimestampUsecs()J
at com.mercury.opal.util.VmwareTimer.getTimestamp(VmwareTimer.java:66)
at com.mercury.opal.util.Timestamp.timestamp(Timestamp.java:345)
at com.mercury.opal.util.Timestamp$1.timeDriftEstimate(Timestamp.java:1214)
at com.mercury.opal.util.Timestamp$1.run(Timestamp.java:1201)
at com.mercury.diagnostics.common.util.InfrequentEventScheduler$Event.run(InfrequentEventScheduler.java:319)
at com.mercury.diagnostics.common.util.InfrequentEventScheduler.runThisEvent(InfrequentEventScheduler.java:620)
at com.mercury.diagnostics.common.util.InfrequentEventScheduler.runEvents(InfrequentEventScheduler.java:598)
at com.mercury.diagnostics.common.util.InfrequentEventScheduler.access$5(InfrequentEventScheduler.java)
at com.mercury.diagnostics.common.util.InfrequentEventScheduler$BackgroundThread.run(InfrequentEventScheduler.java:674)

Resolution: A coding error prevented the probe from recognizing that the platform was 64-bit. The
product will now recognize it as 64 bit.

53383 - detail=args:0 in the point definition turns into an error message

Problem: Every time the value is set to 0 (detail=args:0), the following message appears:

2010-11-08 16:21:20,214 WARN capture.inst [main] Malformed detail '0' argument number out of range.
(Must be integer >= 1)
2010-11-08 16:21:20,214 WARN class com.mercury.opal.capture.inst.compile.CodeSnippetCompiler
[main] Ignoring code snippet '#arg-1.toString()'
com.mercury.opal.capture.inst.compile.ParseException: Encountered "." at line 1, column 7.

Resolution: Works as expected.

56225 - Probe Metrics not available for JBoss Application Server.

Problem: JBoss JMX metrics are missing in the Profiler and the end user UI. Errors in the probe
log indicate an error of some sort when connecting to the JBoss JMX Metric Server MBean.

Resolution: Changed the jar files delivered with the probe to eliminate class duplicates.

56287 - Java probe attempts to open incorrect directory on Turkish system - system metrics are not
generated.

Problem: Java probe attempts to open incorrect directory on Turkish system - system metrics are not
generated.

Resolution: The probe was attempting to open the wrong directory (ppc-aýx instead of ppc-aix). A
change to the code which opens the directory resulted in the correct directory (ppc-aix) being opened.

57326 - Sun 1.5 JVM crashes with Assertion `(*env)->GetDirectBufferCapacity(env, data) >= (offset +
length)' failed

Problem: Sun 1.5 JVM crashes with Assertion `(*env)->GetDirectBufferCapacity(env, data) >= (offset +
length)' failed

Resolution: Modified code to avoid the JVM crash.

58226 - Instrumentation issues with Glassfish App Server

Problem: There are some issues with metrics collection with Glassfish App Server. After instrumenting
the Glassfish App Server it caused the APP server to crash. This was the error seen in the logs:

INFO [com.mercury.opal.common.loader]: Loading modules.properties from:
/opt/MercuryDiagnostics/JavaAgent/DiagnosticsAgent/lib/../lib/modules.properties

HP Diagnostics J2EE Probe 'xxxxxxxx', version: 9.00.77.1123

Could not load Logmanager "com.sun.enterprise.server.logging.ServerLogManager"

java.lang.ClassNotFoundException: com.sun.enterprise.server.logging.ServerLogManager

Resolution: Changed the probe code to delay its initialization, giving time for Glassfish and Java login
to initialize without interference.

.NET Agent

59321 - A feature in Diagnostics .NET agent to limit log folder size does not work.

Problem: .NET generates huge logfiles - even after adding the following to the probe_config.xml file:

Some servers have log directories over 1 GB and some are approaching 2 GB.

Resolution: The code that attempted to limit the logfile size not work and failed silently. Logic problems
with the code were fixed. There is yet an issue with the delete permissions to the log folder. The
customer will need to modify the permissions on the log folder so that the .NET process Account (IIS App
pool Account) has permissions to delete files in this folder.

58912 - .NET agent causes java.lang.NumberFormatException on Diagnostics server when sending
Probe Metrics in Danish locale.

Problem: HP Diagnostics .Net Agent 9.00.77.34620 on Windows 2003 Server with locale set to Danish
regional settings.

Server log reports:

2011-04-07 12:44:12,771: SEVERE athDispatcherHandler: unhandled exception processing HTTP
request for POST /metricdata/?sleep=false&probe=<servername>.1302170136733284&probehost=<servername>.dk
HTTP/1.1: java.lang.NumberFormatException: For input string: "0,002377253"

java.lang.NumberFormatException: For input string: "0,002377253"

at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)

Probe log reports:

2011.04.07.12.44.12.140 [0012] SEVERE ProbeMetrics ProbeMetricsAgent(5896758) caught
exception when sending metrics to uri(<http://10.172.4.112:2006/metricdata/?sleep=false&probe=<servername>.1302167756125077&probeh
ost=<servername>>)

System.Net.WebException: The remote server returned an error: (500) Internal Server Error.

at System.Net.HttpWebRequest.GetResponse()

at Mercury.Capture.ProbeMetricsAgent.Request()

Resolution: Changed the .NET agent to report number with CultureInvariant format.

56526 - Diagnostics Commander taking very long time to startup OR not starting at all in .NET
environment with a large number of unique SQL statements.

Problem: Diagnostics Commander taking very long time to startup OR not starting at all in .NET
environment with a large number of unique SQL statements.

Resolution: Cause - the cause of the problem is that the .NET agent and server do not merge SQL
statements that are unique. For example, the Java agent will take the following SQL statements:

1. select max(toAccount) from Relations where Relationship = 'R' and FromAccount = 23489234

2. select max(toAccount) from Relations where Relationship = 'A' and FromAccount = 23492348

3. select max(toAccount) from Relations where Relationship = 'B' and FromAccount = 12985712

And merge them into a single statement:

select max(toAccount) from Relations where Relationship = ? and FromAccount = ?

The solution is to enhance the .NET agent and server to work the same way as the Java agent.

Enterprise User Interface

59831 - Profiler UI download creates multiple copies of the same jar for the same version under
%TEMP%.

Problem: When downloading the UI jars files (client or probe profiler UI) only the jar file names will be
persisted to the client cache in %TEMP% instead of the complete path of the URL from where it was
downloaded. Before this fix, the jar name contained the probe name which increases the number of
downloads and wastes storage under %TEMP%.

Resolution: The code no longer downloads the same version multiple times.

59783 - Network bytes in the range of GB per second on AIX.

Problem: In the Diagnostics UI -> Standard View - Hosts, sometimes the information for the Network
bytes utilization shows GB per second, which does not seem a feasible metric value.

Resolution: Network I/O KBytes/Second shows the total network bytes of all network interfaces as well
as the loopback interface, which cannot be measured externally. The benchmark for the Diagnostic UI is
that it needs to match what the OS reports as the total network I/O bytes (some OSes include loopback
and others don't).

59173 - Cannot reset Availability Threshold after setting to "No Threshold".

Problem: After setting the Probe Availability threshold to "No Threshold", you cannot go back and reset
the Availability threshold for that probe.

Resolution: Corrected dialog creation so no NPE will occur.

59046 - Even though `Availability' metric is showing in the inspector (details pane), it does not turn
yellow/red.

Problem: - Even though `Availability' metric is showing in the inspector (details pane), it does not turn
yellow in the inspector window correctly.

Resolution: The metric will properly show yellow in the inspector window.

58688 - Go to any view and select multiple metrics, then leave the view and come back. The graphs are
sometimes messed up.

Problem: - Go to any view and select multiple metrics, then leave the view and come back. The graphs
are sometimes messed up.

Resolution: Internal logic error was corrected.

53875 - Want to share a view between applications

Problem: Want to share a view between applications. When a view is created inside application A,
it should be easy to share it with all other applications or specific applications so when connecting
to other applications, it's easy to run the same view.

Resolution: Regardless of the application in which the application is created, as long as specific entities
are not selected (topN is not my Selections) this change will allow a view to be copied and used between
applications.

55258 - NPE and HTMLEditorKit prevents UI from starting more than once

Resolution: Fixed this JRE issue (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6993073) by
implementing the workaround ( http://bugs.sun.com/bugdatabase/view_bug.do?but_id=6993691) in
Diagnostics so the JRE does not throw an exception.

Workaround: But it is important to note that since the Java probe install includes the Profiler UI - then
each probe where you run the Profiler UI also needs to be updated or patched to get this fix. Otherwise
the Profiler UI applet will only load once in the browser. You can download a patch for Java probe
versions 8.0x or 9.0x and the fix is also included if you upgrade the Java probe to version 9.02.

System Metrics

59122 - Network metric values are too high on SunOS on VMware.

Problem: Network metric values are consistently too high when SunOS is running under VMware.

Resolution: Modified algorithm to take into account the virtual environment to return correct metric values.

What's New in 9.01

Diagnostics 9.01 has a number of defects fixes and a number of new features shown below. Note that the
defect tracking number shown (for example 35266) is generally prefixed with QCCR1I.

Platform Support Changes

New Features

.NET Agent - Support multiple application domains with the same name and distinguish them so that
the data from them does not get aggregated together. (42733)

Background: Change the format for the ASP.NET AppDomains which were previously not qualified
with the IIS Path.

Description:

Old Probe_config.xml Configuration

</appdomain>

The configuration format does not provide a way to distinguish the 3 distinctly configured CallChain
applications in IIS. The result of this was that you had to enable all (CallChain AppDomains) or
disable all. This is not a desirable level of control to enable\disable Web Applications. More so, the
probes instantiated by all the CallChain AppDomains were named exactly the same and so the server
requests from these applications got attributed to the single consolidated probe on the server. The probe
metrics were also averaged over 3 completely independent instances which would be incorrect data
presented to the user.

This feature changes the format for ASP.NET(IIS) AppDomain configuration format in the
probe_config.xml file to enable distinguishing the AppDomains by qualifying it with the IIS
configuration path.

The new configuration for the 3 CallChain applications would be as follows

NEW Probe_config.xml Configuration

</appdomain>

</appdomain>

<points file="WebSite2-CallChain.points

Benefits: Functionality

Integrations and Enterprise UI - Enhance Diagnostics from within BSM to include the Help links
(48575)

Background: The help menu including "Help on the View" is disabled when bringing up Diagnostics UI
from within BSM. This means users can only access Diagnostics help from the BSM menu and they lose
the context sensitive help links from the Diagnostics UI.

Description: Enabled the help menu links in the Diagnostics UI when bringing up Diagnostics from
within BSM.

Benefits: Usability.

Defect Fixes

Server

47433 - IllegalStateException during OMi registration (BSM/Diagnostics Registration) in log file

Problem: This error gets logged when doing registration of BSM/Diagnostics but it does not indicate a
real problem. A bad code path was doing a send with an event channel integration error (along with a
successful BAC registration), but then continuing to try to ALSO "sendSuccess". Doing two responses to
one request was the problem.

Resolution: The unnecessary 2nd send was the one that was failing. Now it is avoided.

48066 - The discovery that adds probes/server requests/hosts to an Application when a Business
Transaction is added to the Application only works for probes (SRs/hosts) that are not directly connected
to the commander.

Problem: The discovery that adds probes/server requests/hosts to an Application when a Business
Transaction is added to the Application only works for probes (SRs/hosts) that are not directly connected
to the commander.

Resolution: The new feature of automatically adding entities to apps will now work on probes directly
connected to the commander.

47650 - Newly created Business Transactions briefly show a latency of zero with big numbers for
min/max.

Problem: Immediately after a Business Transaction is created via the Diagnostics UI or BSM it shows up
in Diagnostics with latency of 0. The latency looks strange because it shows zero
values and very high/low numbers for min/max. After a few seconds the latency numbers go away (until
real numbers come in).

Resolution: The Business Transaction will only show latency now when an actual value is present and
ready to show.

Java Agent

48656 - Getting Mismatch Serialization UID

Problem: When adding an instrumentation point with regular expression including all classes and
methods, client application was failing with mismatch serialization error. Specifying a specific class and
method avoided the problem.

Resolution: To avoid application crashes we now do not add method wrappers for serializable classes. At
the same time the user gets precise control over where the wrappers will be added.

48962 - Probe must not override good information with "Unknown"

Problem: Customers sometimes see "Unknown" instead of the actual web service fields (for example they
may see the web service operation as "Unknown").

Resolution: The probe now reports the best information it can. If non-Unknown information was
captured at some point in the chain, then we will use it.

49374 - For a single outbound call, the Outbound calls screen can show multiple entries

Problem: For a single outbound call, the Outbound calls screen can show multiple entries. This was in
the case of nested outbound calls, i.e. when an outbound instrumentation point was hit multiple times
consecutively.

Resolution: Fixed the code so that only one entry is shown.

30602 - Wrong root method name is shown for the call profile of a cross-VM callee side server request

Problem: Wrong root method name "Outbound Call" is shown for the call profile of a cross-VM callee side
server request.

Resolution: The right root method name will now be shown.

49460 - Service topology does not connect the SOAP over JMS web services.

Problem: SOAP over JMS Web Services were not connected in the Service topology screen.

Resolution: The code problem has been fixed and now they are connected.

.NET Agent

33682 - CLR Issue with instrumentation (fixed for CLR 4.0 only) - Hp.Profiler.dll is loaded into
applications not configured for monitoring.

Problem: The .NET agent inspects all .NET applications which come up for instrumentation by verifying
scope defined in the probe_config.xml. This is how the .NET profiler works; it invokes the agent for every
.NET application instantiated. Some applications (read executables) are fleeting, for example the Visual
Basic compiler and C# compiler which get triggered in certain deployment scenarios in IIS. We are
unable to handle the fleeting nature of such applications as they exit even before we have a chance to
verify scope. Also there are applications like the Visual Basic compiler (mainly Microsoft binaries) which
do not make sense to try and instrument or verify whether they are in scope. Verifying scope adds
considerable start-up overhead. The .NET agent should maintain a list of such applications (preferably
configurable) so that we recognize the futility of trying to instrument these processes right at the start
and ignore them.

Resolution: Changed the return value for Initialize for CLR\.NET V4 to
CORPROF_E_PROFILER_CANCEL_ACTIVATION for Applications which are NOT configured to be
monitored. This will release the HP.Profiler.dll from the process memory. This is not available with
earlier version of the profiler API hence cannot be solved for CLR\.NET V2

Collector

47933 - Diagnostics Collector - creates/updates node CI with wrong (unqualified) primary DNS name
attribute.

Problem: The DB Collectors were sometimes reporting the unqualified DB host names to the Diagnostics
Server (and hence the node CI was created with the unqualified name)

Resolution: Added comments to the configuration files of both DB Collectors and the HP Diagnostics
Installation and Configuration Guide to instruct the user to use the fully qualified host name when
configuring the DB Collectors.

Enterprise UI

49580 - Service Health 360 View Drill to Probe Group Summary opens with incorrect probe group
context

Problem: Diagnostics Probe Group Summary opens in context of probe group that was not selected in the
360 view.

Resolution: Diagnostics Probe Group Summary opens in context of the probe group selected in the 360
view.

48539 - Graph is blank on the new "Server - Basic Metrics" view when first navigated to as a top level
view

Problem: Graph is blank on the new "Server - Basic Metrics" view when first navigated to and when
navigated to as a top level view.

Resolution: The default graph is not blank and the graph shows the throughput data.

30577 - Call profile wedding cake for JMS onMessage() does not show the time for the onMessage() itself

Problem: The call profile is displayed for queue://queue://FX. However, the top level bar/layer in the
wedding cake does not show the time for the onMessage(). Instead, it shows the times for the methods
called by the onMessage().

Resolution: Re-architecting the probe made this change possible.

49424 - Business Transaction view should not show CPU column

Problem: Don't show CPU column because it isn't used for business transactions.

Resolution: Removed column from screen definition.

Integrations

48259 - HIs missing "sec" units.

Problem: Health Indicators from Diagnostics missing "sec" units.

Resolution: Added "sec" to Synthetic Business Transaction HIs.

48318 - There are 2 indicators in HPBSM\AppServer\webapps\site.war\bam\conf\repositories\external
\diagnostics\indicators\def.xml that have same name on the same CI type

Problem: Duplicate Health Indicator definition.

Resolution: Removed the duplicate TransactionManager definition on diagnosticsprobe.

49972 - Diagnostics Server Linux 64-bit Agent Registration Fails with BSM 9.0x

Problem: The Agent Registration with BSM 9.0x fails with the Diagnostics Commanding Server Linux
64-bit version.

Resolution: The <install dir>/bin/swith_ovo_agent.sh script could not find the path of the Agent 64-
bit libraries. The script was using /opt/OV/lib when it should have been using /opt/OV/lib64. Set lib64
directory.

Documentation

49236 - Setting up SiteMinder module

Problem - Problem with the configuration guidelines found in the Diagnostics Installation guide for
setting up SiteMinder:

Set up Apache Server 2.2 with reverse proxy (reverse proxy redirection works fine) to Diagnostics

Enable the SiteMinder Agent in the Apache Server

Configured the SiteMinder Module in the jaas.configuration

When entering into the SiteMinder site and provide credentials, the Browser shows "Internal Server Error".

Resolution: Updated the 9.01 Installation Guide, Appendix B, section on "Using Reverse Proxy with
SiteMinder JAAS LoginModule" in the example of Apache reverse proxy setup on HP-UX, updated the
procedure as follows:
Edit the Apache configuration file httpd.conf and add the following properties:

ProxyPass /siteminderagent !

ProxyPass / Error! Hyperlink reference not valid. of Diagnostics Server>:2006/
(2006 is the default Diagnostics Server port, use the port configured for your Diagnostics Server)

ProxyPassReverse / Error! Hyperlink reference not valid. of Diagnostics Server>:2006/
(2006 is the default Diagnostics Server port, use the port configured for your Diagnostics Server)

What's New in 9.00

Diagnostics 9.00 has a large number of defects fixed and a number of new features shown below.

New Features

Business Transactions

Diagnostics can now automatically detect and report on "Business Transactions", identifying
cross VM dependencies and reporting the time taken along the different paths of the
transaction and showing the topology in the UI.

The configuration of these transactions can be done in either the Diagnostics UI or the
BSM UI.

The Business Transactions can be viewed in either the BSM UI or the Diagnostics UI
as a topology or table view.

In addition, users will be able to see server request topologies in Diagnostics (not
previously available).

Business Service Management integration

We have greatly improved integration with the BSM framework including the population
and synchronization of many Configuration Items (CIs) within the ODB.
In addition, we are populating Key Performance Indicators (KPIs) and Health
Indicators (HIs) inside of the BSM Dashboard.

Business Transactions can be viewed in the BSM Transaction Management UI and can be used
to track service levels with SLM.

UI Enhancements

Two new View Groups

Aggregate View Group - entities aggregated by probe group (useful in cluster environments)

Transactions View Group - Business Transactions (All Users) and Synthetic Transactions
(BPM)

New Java Probes and .NET Probes views under Standard views

SQL Statements by Probe view added to Standard views

Outlook Style tabbed pane now organizes the view groups

Virtual Hosts - VM Guest value is displayed in Host Topology view

Open in Custom View - User can create a custom view that can be opened in context for a
selected entity. (For example > Save view for a probe and open it in context of any probe,
this is similar to opening a probe in the Probe Summary view.)

Chart Groups - In any Standard entity view, the user can group the chart trends
by metric or by entity.

View context sensitive help for each UI view through use of new Help menu item
"Help on View"

User can export data from a Diagnostics view into a CSV file

Export Selected chart data to CSV

Export the data zoomed to in a chart in Standard views

Exports the trend for all charts in summary views

The Mercury System user can use Diagnostics in a large deployment to manage System
Health

Show number of probes per probe group and number of probes per mediator (Capacity View)

User can see only the probes of interest in the Diagnostics UI screens (System Health)

UI configurations (ui.properties) for large deployments

Set the Top N probe entities query parameter

Throttle server query frequencies by query type

CAM Discovery Policy informs UI to Include probe's entities in top level views

Default setting for all applications

Informs the UI to not filter by application below the probe level

Diagnostics will automatically discover Business Transactions CIs based on server requests-
Rule based definition of Business Transactions

.NET agent enhancements

Scalability improvements - The .NET agent deployments can scale more with the
Diagnostics server with the use of the .NET Probe Aggregator Service on the agent system.
This reduces significantly network I/O on both the agent and server systems.

Monitoring of asynchronous .NET applications; Sending and receiving messages
using MSMQ

WCF features match those of other protocols

Diagnostics .NET agent will provide collection data to the server (LWMD)

.NET agent collects more metrics OTB and the user can easily add new metrics on demand.

CLR 4.0 .NET environment support

.NET agent will support parameter capture

.NET agent captures parameters of the first method that sees an exception thrown

.NET agent has enhanced correlation capability to outbound http calls made to Java
components

Java Agent enhancements

New Collection Leak Pinpointing feature automatically detects memory leaks. This feature
is incredibly cool!

Java agent correlation across multiple threads - In complex Enterprise Service Bus
solutions like Tibco Active Matrix, WebLogic's AquaLogic and others - a single
"server request" can span multiple threads within the ESB. Until now, Diagnostics
could not correlate the server request across the threads, now it can show the total
latency across the threads. Initially, we support WebLogic AquaLogic and will add
others (like Tibco) as customer demands dictate.

Cross VM correlation can be configured through instrumentation to support any protocol,
including home grown generic TCP communication.

User can see Server Request topology and Business Transaction flow from a .NET probe to a
Java probe based on an HTTP call (and back).

Other misc enhancements:

CORBA Cross MV Tracing

User can select probe metrics to be included in the LR, PC offline analysis file.

System Requirements

The HP Diagnostics Installation and Configuration Guide contains detailed information about system
requirements. This guide is available in a PDF version (Diagnostics_Install_Guide.pdf) located on the
installation disk or in the Diagnostics Server download package. Examples of typical system requirements
are provided below for the Diagnostics Server.

Examples of Requirements for the Diagnostics Server

Diagnostics uses the Java 1.6 JVM for the Server (and the Collector).

Java 1.6 JVM is supported on the following operating systems and requires the patches listed below.

For the most recent information on supported environments refer to the Diagnostics Product Availability
Matrix at http://support.openview.hp.com/sc/support_matrices.jsp.

The following table shows an example of typical system requirements for the host of a Diagnostics Server
with different numbers of Java Probes.


Platform	Item	Up to 50 Java probes	Up to 100 Java probes	Up to 200 Java probes
Windows	CPU	2x 2.4 GHz	2x 2.8 GHz	2x 3.4 GHz
Windows	Memory	4 GB	4 GB	4 GB
Solaris	CPU	2x Ultrasparc 3	2x Ultra Sparc 4	2x Ultra Sparc 4
Solaris	Memory	4 GB	4 GB	4 GB
Linux	CPU	2x 2.0 GHz	2x 2.4 GHz	2x 2.8 GHz
Linux	Memory	2 GB	4 GB	4 GB
HP-UX	CPU	PA-RISC 2x 650 MHz	PA-RISC 2x 699 MHz	PA-RISC 2x 750 MHz
HP-UX	Memory	2 GB	4 GB	4 GB
All	Java Heap	512 M	750 M	1280 M
All	Disk	4 GB per probe
Notes regarding the test environment: Call profile (depth of method calls) for each Server Request: 5 Number of unique Server Requests per probe: 23

The following table shows an example of typical system requirements for the host of a Diagnostics Server
with different numbers of .NET Probes.


Platform	Item	Up to 10 .NET probes	Up to 20 .NET probes	Up to 50 .NET probes
Windows	CPU	1x 1.0 GHz	1x 2.0 GHz	2x 2.4 GHz
Windows	Memory	768 MB	1 GB	3 GB
Solaris	CPU	1x Ultrasparc 2	2x Ultra Sparc 2	2x Ultra Sparc 3
Solaris	Memory	1 GB	1.5 GB	3 GB
Linux	CPU	1x 1.0 GHz	1x 2.0 GHz	2x 2.4 GHz
Linux	Memory	768 MB	1 GB	3 GB
HP-UX	CPU	1x 1.0 GHz	1x 2.0 GHz	2x 2.4 GHz
HP-UX	Memory	768 MB	1 GB	3 GB
All	Heap Size	350 M	700 M	1400 M
All	Disk	3 GB per probe

Information on System Impacts When Probed (.NET Probe)


Item	Minimum
Latency	+3% while CPU < 50%-once the CPU starts saturating, latency overhead increases
Memory	60MB additional RAM
CPU	+5%
Disk Space	200MB free disk space is required for the probe install
Network I/O	+3% to +5% (assuming a normal ASP.NET application with a remote database Backend)
Disk I/O	Impact should be statistically insignificant
Throughput	< 1% reduction while CPU < 50% - should not exceed 15% reduction even under peak load Be careful with other metrics once throughput is impacted - as the application is doing less work, results are not directly comparable
RAM utilization	Baseline footprint increase of up to 20MB per worker process Note: This is quite difficult to measure accurately.

Information on System Impacts When Probed (Java Probe)


Item	Minimum
-Xmx	Add 40MB
Disk Space	200MB free disk space is required for the intial probe install. Note, more space may be required during runtime due to the creation of logfiles and classmap. For large applications, it is recommended to have an additional 200MB available per probe for logfiles and classmap data.
Latency	+3% while CPU < 50%-once the CPU starts saturating latency overhead increases
CPU	+5% to +10%
Network I/O	+3% to +5% (assuming a normal Java EE application with a JDBC, RMI, or Web-services Backend)
Disk I/O	Impact should be statistically insignificant
Throughput	< 1% reduction while CPU < 50% - should not exceed 15% reduction even under peak load Be careful with other metrics once throughput is impacted - as the application is doing less work, results are not directly comparable
RAM utilization	Baseline footprint increase of about 40MB

The requirements and general impact on the system depends on the monitored application and on the
probe configuration. The values listed above are examples for a default probe configuration only.

Notes and Limitations

Notes and limitations are provided for the following component areas. Note that the defect tracking number
shown (for example 35266) is generally prefixed with QCCR1I.

Java Agent

Important Note: If you use the Payload Capture feature on SOAP faults please note that those payloads
can contain sensitive information such as credit card numbers. Payload Capture is enabled by default.
If there is an issue with sensitive data being captured you can turn off Payload capture by setting the
max.soap.payload.bytes property in dispatcher.properties on the agent to zero like so:

max.soap.payload.bytes=0

When the dynamic property enable.stack.trace.sampling is set to "auto" (the default value), it activates
stack trace sampling as described below: (38822) (43937)

On any Java 1.5 implementation with the following limitations:

For HotSpot JVM, version 1.5.0_04 or later is required

For JRockit JVM, JRockit version R27.4 or later is required

On any Java 1.6 implementation with the following limitations:

For PA-RISC HP-UX, JRE version 1.6.0.03 or later is required

"Too many open files" erros after deploying probe on an IBM Java 6 64-bit JVM (60289)

A bug in some versions of IBM's Java implementation may cause the application to crash with a "too
many open files" error when used with Diagnostics Agent.

The affected JVMs do not run any object finalizers when invoked with a -javaagent option pointing to an
agent which declares its capability to instrument classes dynamically ("Can-Redefine-Classes" is set to
true in the manifest file).

Workaround: Invoke the Diagnostics Agent without using "-javaagent". After running the
jreinstrumenter for the JRE in question, use the java options recommended by the jreinstrumenter with
the -javaagent option removed, and with <probe_install_dir>/classes/boot directory added to the -
-Xbootclasspath. For example:

-Xbootclasspath/p:/opt/MercuryDiagnostics/JavaAgent/DiagnosticsAgent/classes/IBM/1.6.0/instr.jre:
/opt/MercuryDiagnostics/JavaAgent/DiagnosticsAgent/classes/boot -Xshareclasses:none

Special configuration needed to support SAP JVM NetWeaver 7.1 and later (43388)

Because NetWeaver 7.1 runs in a clustered environment, you will need to do one of the following in order
to distinguish the probes in the cluster:

Find a way to set the probe.id for each individual server process in your cluster (an expert SAP
administrator might be able to help).

If the above is not possible, then you need to specify the keyword %0 in the probe name. Doing
this will name each probe in the cluster uniquely. For example, if you specify "-
Dprobe.id=myProbe%0" then the first probe that comes up will be called "myProbe0", the second
one "myProbe1" and so on.

There is a potential issue on HP-UX 11.23 with IBM WebSphere: When multiple probes are installed on
the same system, it can happen that the probe's communication port (35000) will be overwritten with
each startup of the probe. In this case, simply specify a different port range for each of the probes in
etc/webserver.properties, for example:

jetty.port=36000

jetty.max.port=36100

Or specify the above parameters on the app server's startup configuration (via -D). (44062)

Using the Heapwalker feature with JRockit JVM version 27.3 may cause the application to crash.
Versions 27.2 and 27.4 and higher work as expected, so the problem is only with version 27.3. Please
upgrade to a higher version of JRockit to fix this problem. (43993)

When instrumenting an IBM 1.6 JVM on z/OS only, using the output of the JRE Instrumenter, the JVM
will fail to start with a java/lang/NoClassDefFoundError exception. (50969)

To correct this issue, modify the

-Xbootclasspath parameter by appending ":<probe_install_dir>/classes/boot"
substituting for <probe_install_dir> appropriately.
In particular note the required colon after instr.jre.

For example, if the output of the JRE Instrumenter was:

"-Xbootclasspath/p:/opt/JavaAgent/DiagnosticsAgent/classes/IBM/1.6.0/instr.jre"
"-javaagent:/opt/JavaAgent/DiagnosticsAgent/lib/probeagent.jar"
-Xshareclasses:none

Change it to:

"-Xbootclasspath/p:/opt/JavaAgent/DiagnosticsAgent/classes/IBM/1.6.0/instr.jre:
/opt/JavaAgent/DiagnosticsAgent/classes/boot"
"-javaagent:/opt/JavaAgent/DiagnosticsAgent/lib/probeagent.jar"

-Xshareclasses:none

When the Diagnostics/TransactionVision Agent is run in "dual" mode, there is a limitation on JDBC
calls. "Dual" mode means that both Diagnostics Java probe and TransactionVision Java sensor are
enabled on the system. In this configuration, Diagnostics has the following limitations:

1) No data will show up from nodes in "dual" mode in the "SQL Statements" view.

2) When drilling down to a Call Profile, JDBC calls will not show the SQL statement in the Arguments of
the call.

This problem will be fixed in a future release of Diagnostics. (42989)

GC Time Spent in Collector metric may be inaccurate (JRockit JREs only)

The problem is caused by a bug in JRockit JRE which reports the time spent in GC in nanoseconds
rather than in milliseconds, as specified.
Workaround: either upgrade JRockit to version 1.5.0_10, build
R27.2.0 (or later) or modify the Rate setting as follows:

In <probe_install_dir>/etc/metrics.config, change "[0.1]" to "[0.0000001]" in the line which defines "GC
Time Spent in Collections" metric. For example:

Java\ Platform/java.lang\:type\=GarbageCollector,*.CollectionTime = RATE[0.0000001](GC Time
Spent in Collections|percent|GC) (42344)

If the following WARN message is found in the probe.log file on the probe system:

2006-11-28 07:07:27,171 WARN com.mercury.opal.capture [ExecuteThread: `8' for queue:
`weblogic.kernel.Default'] Maximum number of SQL queries cached (4096). The values of some prepared
SQL queries will be lost. See sql.cache.size in capture.properties.

Then you will need to increase the sql.cache.size in the capture.properties file on the probe system.
(40639)

Do not run jreinstrumenter from the Java Agent Setup Module if you are installing the probe only in
order to get the standalone system metrics agent. (42069)

By default, Diagnostics does not monitor server requests that always execute in under 51 milliseconds.
These requests are trimmed-no information is captured about them. SQL statement executions made
from these trimmed requests are not recorded, even if those same SQL statements are timed and
recorded in the context of executing other server requests. In addition, the probe-level layer breakdown
does not include time taken by trimmed server requests.

An exception to this is in a case where, on at least one occasion, a server request takes longer than 51ms
to execute. Future executions of that server request are recorded, even if the subsequent requests are
faster than 51ms. The reason for this behavior is to report accurate averages (and not mislead the user
into thinking that this request only ran once or twice when in actual fact it is constantly running, just
very quickly). This "Always Record" flag lasts for 1 hour from the last time an execution over 51ms was
seen.

You can redefine the 51ms trimming threshold. For the Java Probe
integrated with LoadRunner or Performance Center, you configure this setting in the
<diagnostics_server_install_dir>\etc\trimming.properties file. For the Java Probe in all modes, you
configure this setting in the minimum.fragment.latency property in the
<probe_install_dir>\etc\dispatcher.properties file. (40631)

A defect in the JVM on Linux (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6330858) results in
the thread CPU times being the same for all threads in BEA WebLogic 9.0. This bug was fixed in JDK
1.5.0_07. (40391, 39387)

The Java Probe causes core dump at startup of WebLogic 9.1 when used with JRockit VM version
150_04. The JRockit bug is fixed on jdk1.5.0_06. (38545)

By default, for performance reasons, Diagnostics does not capture target information for Database calls.
Therefore, these calls do not show up in the Outbound Calls view. You can enable it as follows:

For version 7.0 and higher of the Java Probe, set create.database.fragmentArcs=true in the
probe's dispatcher.properties file.

Once capturing of Outbound database calls has been enabled, these calls will be displayed in the
Outbound Calls view. (40722)

VM Heap Breakdown is based on an experimental api (JVMPI) in the JVM and is not
expected to work in the following JVMs:

Sun 1.4.2_01: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4861809

Sun 1.4.2: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4899339 {open}

IBM JREs in general do not have a stable API implementation for this API

Running the profiler directly on z/OS is not supported. The script "profiler.sh" has been removed in the
7.50 version of the z/OS probe, it will exist in previous versions but cannot be successfully run on z/OS.
To run the profiler for a probe on a z/OS system, do so from a platform other than z/OS. (42369)

.NET Probe

By default, Diagnostics does not monitor server requests that always execute in under 51 milliseconds.
These requests are trimmed-no information is captured about them. SQL statement executions
made from these trimmed requests are not recorded, even if those same SQL statements are timed
and recorded in the context of executing other server requests. In addition, the probe-level layer
breakdown does not include time taken by trimmed server requests.

An exception to this is in a case where, on at least one occasion, a server request takes longer than 51ms
to execute. Future executions of that server request are recorded, even if the subsequent requests
are faster than 51ms. The reason for this behavior is to report accurate averages (and not mislead the
user into thinking that this request only ran once or twice when in actual fact it is constantly running,
just very quickly). This "Always Record" flag lasts for 1 hour from the last time an execution over 51ms
was seen.

You can redefine the 51ms trimming threshold. For the .NET Probe in all modes you configure this
setting in the <diagnostics_server_install_dir>\etc\trimming.properties file. All .NET Probe trimming
configuration is done in the <.NET_ probe_install_dir>\etc\probe_config.xml file. (40631)

For .NET Probes, set create.database.fragmentArcs=true in the server.properties file for the
Diagnostics Server in Mediator mode. You should also use this workaround if
enable.probe.aggregation in the Java probe has been changed from its default value of true to
false.

Once capturing of Outbound database calls has been enabled, these calls will be displayed in the
Outbound Calls view. (40722)

On platforms where Windows Process Activation (WPAS) is installed, the .NET Diagnostics agent
uninstall has an implicit runtime dependency on up to four "listener adapter" services. During the
uninstall, MSI pops up a "The following processes need to be closed before continuing..." dialog if any
of the listener adapter services are started. Stopping them (temporarily) allows the uninstall to
continue. However, the services do NOT have to be stopped in order for removal to end successfully.
The user can select the "Ignore" button on this dialog and continue uninstallation. (38151)

If you have a problem displaying probe metrics by .NET Agent. If you have done the configuration
described in the KnowledgeBase article
http://support.microsoft.com/default.aspx?scid=kb;EN-US;282884
Diagnostics .NET agent will not be able to show probe metrics.

Integration (BSM, LoadRunner, Performance Center, TransactionVision, SaaS)

Diagnostics Server does not work with IIS Basic Authentication with Business Availability Center and
BSM Reverse Proxy Server. (43987)

During installation of Operations agent components, certificate requests from Diagnostics (and IA, and
SiteScope) nodes are blocked at Load Balancer/Reverse Proxy if BSM has been configured for HTTPS
communication. (QCCR1A122094)

During installation of Operations agents, a certificate request is sent to the certificate server. The
protocol used for the request is HTTP. If the BSM Reverse Proxy/Load Balancer is configured for HTTPS
communication, it blocks all HTTP communication including the certificate request.

Workaround. Generate a certificate manually and install it manually on the IA/SiteScope/Diagnostics
node. You can refer to the topic "Configure HP Operations Agent manually" in the HP BSM Integration
Adapter Installation and Upgrade Guide in the BSM documentation library and do something similar
for Diagnostics.

Offline vs. Online. The following features and functionality in LoadRunner Offline Analysis are different
from the Diagnostics Online.

Data in the profiler that is not sent into the Diagnostics Server will not be in the offline analysis
after Performance Center/LoadRunner runs. This includes LWMD, Heap Breakdown, Allocation
Analysis, Exceptions, SOAP Faults and SOAP payloads.

Oracle 10g data will not show up in offline analysis.

Instance trees will not be available in the offline analysis only aggregate trees after the needed
drill down.

When configuring Real User Monitoring in Business Availability Center to use a Page definition
including parameters, Diagnostics will not be able to make a match unless parameter capturing has
been enabled. To enable this option on the Java Probe, list all desired parameter names in reverse
alphabetical order in the args_by_class property in auto_detect.points under the "[HttpCorrelation]"
section. (40496)

In BSM's Transaction Management Admin UI > Monitoring tab > Search Criteria, when the Type
dropdown list is expanded, duplicate or triplicate Server Request types are shown. (60740)

HP Performance Center offline files are kept by default. To manage offline files, you need to configure
the Diagnostics Servers in Mediator mode so that they delete these files. You do this by setting the
property distributor.offlinedelivery.preserveFiles to true in the
<diagnostics_server_install_dir>/etc/server.properties file. When set to true, this property causes the
run-specific "offline" files stored in the server's data directory to be retained for the amount of time
specified in the facade.run_delete_delay property in the server's webserver.properties file (default period
is 5 days). During this retention period, the run can be successfully collated. Sometime after the
retention period has ended, the associated offline files will be deleted from the system. (40739)

Performance Center users that drill to Diagnostics get full admin privileges to the Diagnostics Server
and to the Probes that are connected to it. All restricted actions (for example, changing thresholds,
alerts, and Custom Attributes) are accessible by all Performance Center users. Furthermore, every
custom screen created by a Performance Center user is shared by all Performance Center users. (40133)

Starting in Diagnostics 7.0, many instrumented methods have been flagged when-root-rename in
auto_detect.points to prevent many spurious and uninteresting server requests from being created and
displayed in the UI. Should these methods execute outside the context of another server request, they
will still be recorded, but into a pseudo server request with the name "Background - <Layer>", where
<Layer> is the layer name for the method.

For example, the Background JDBC connection testing that WebLogic runs used to be reported into a
few separate server requests, such as netJDBCPreparedStatement.executeQuery(), but will now be
recorded as invocations of a "Background - Database" pseudo server request.

In addition, when using LoadRunner, these new pseudo server requests will not appear in LoadRunner
Offline Analysis.

Should you wish to keep the old behavior for a particular instrumentation point and see these entries in
LoadRunner Offline Analysis, carefully remove the when-root-rename detail parameter from the
auto_detect.points. (42127)

When Diagnostics is integrated with HP Software-as-a-Service (SaaS), you must log on through Business
Availability Center when viewing data for customers other than "Default Client". Failing to do so will
cause several subtle issues with how data is reported. You can still use the standalone login to view the
"Default Client" data. (42178)

LoadRunner Collate fails when the Diagnostics Server was restarted during Performance Center
run/load test. (34682)

Collectors (Oracle, SAP, MQ, SQL Server)

To maintain accurate MS SQL Server metrics, the database option AUTO_CLOSE must be set to OFF.
If AUTO_CLOSE is set to ON, MS SQL Server metrics will show up with incorrect and negative values
after certain database operations (bcp, backup, shrink, etc) (43075).

NPE for legacy (pre-9.02) MQ collector data. (54829)

Workaround. MQ channel data will populate in the BSM RTSM when 9.02 MQ collector is installed.

JAVA Profiler

Starting with Diagnostics 9.0, the JAVA Profiler requires JVM 1.6 to run. However, on HP-UX, the
default JVM that is installed with the Java Profiler is 1.5. Therefore in order to run standalone
Java profiler, the following must be performed. NOTE - The Java Profiler runs fine on
HP-UX when launched from the enterprise UI. To run the Java profiler in standalone mode,
do the following:

Set JAVA_HOME to your java 1.6 installation location

export JAVA_HOME=<java 1.6 home directory path>

example: export JAVA_HOME=/opt/java6

Run the java profiler: $PROBE_HOME/bin/profiler.sh &

NPE and HTMLEditorKit prevents UI from starting more than once (55258)

Fixed this JRE issue (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6993073) by implementing
the workaround ( http://bugs.sun.com/bugdatabase/view_bug.do?but_id=6993691) in Diagnostics so the
JRE does not throw an exception.

But it is important to note that since the Java probe install includes the Profiler UI - then each probe
where you run the Profiler UI also needs to be updated or patched to get this fix. Otherwise the Profiler
UI applet will only load once in the browser. You can download a patch for Java probe versions 8.0x or
9.0x and the fix is also included if you upgrade the Java probe to version 9.02.

.NET Profiler

When running the .NET Profiler under locales that use an Asian character set, the default font size may
be too small. In such cases, change the text size used by the Web browser. (43070)

Diagnostics Servers

Server Install fails - Permission denied. (51729)

If the Diagnostics commanding server will be integrated with Business Service Management 9.00 or
later, root access is required during the Diagnostics Server installation. Root access is required for the
installation of the OM Agent and IAPA component.

Workaround. If you need to install the Diagnostics Server without root access you can chose to not install
these two components and install them later manually. When you see the dialog box: OM Agent and
IAPA component installations leave the box unchecked and install later

When enabling HTTPS between Diagnostics components the user should monitor the
<install_dir>/MercuryDiagnostics/server/log/jetty.log for warnings similar to:

2008-11-17 15:33:07,528: WARNING : WARN!! [RangeSocketListener-
69]org.mortbay.http.SocketListener.isOutOfResources(SocketListener.java:358)22> OUT OF THREADS:
RangeSocketListener@0.0.0.0:8443

2008-11-17 15:33:35,582: INFO : EVENT [RangeSocketListener-
14]org.mortbay.http.SocketListener.isLowOnResources(SocketListener.java:325)04> LOW ON
THREADS ((200-198+7)<10) on RangeSocketListener@0.0.0.0:8443

Workaround. If these messages appear, increase the value of jetty.threads.max by increments of 100 in
the <install_dir>/MercuryDiagnostics/server/etc/webserver.properties file.

Continue to monitor and increase if necessary. (44007)

After configuring the Diagnostics Server in Mediator mode, if it appears missing or inactive in the
Diagnostics Server in Commander mode view, then it is possible that "commander.url" in
server.properties has an ending "/" on it. For example, if you open server.properties on the Diagnostics
Server in Mediator mode and set to commander.url=http://amkisty01:2006/ instead of
commander.url=http://amkisty01:2006 (Note that the difference is the appending /), then the Diagnostics
Server in Mediator mode will appear missing or inactive. (40527)

Broadly scoped allocation instrumentation may fill up perm-gen and cause the VM to crash. Users
should avoid widely scoped instrumentation and instead make instrumentation as narrow as useful to
minimize system impact. (39339)

When average latencies are less than 50ms, users may see CPU time slightly higher than latencies
because of resolution differences. (39690)

Entity purging results in contribution/breakdown not summing up to the total because the deleted
entities data was already rolled up and is not recalculated at this point. (39344)

Running the Diagnostics Server from a network drive, or configuring it to store the archive on a network
drive, is not supported.

When you configure the Diagnostics Server to run only in SSL mode, it only affects port 2006. The
Diagnostics Server also has an embedded Diagnostics Probe (for internal troubleshooting purposes) that
listens, as usual, on port 35000. If you are trying to lock your environment to SSL only for security
purposes, you will also need to re-configure that embedded probe to listen only over SSL.

User Interface

With IE 8 the Maintenance Link is missing on the Diagnostics Enterprise UI when launched from within
BSM UI (BMS and Diagnostics are running on the same system). (55189)

Workaround. Close the BSM UI and the Diagnostics Standalone UI, and re-launch the Diagnostics
Standalone UI. Also note it works fine when running with IE7 or launched stand-alone in IE8 (not inside
of BSM).

NPE and HTMLEditorKit prevents UI from starting more than once (55258)

Enterprise UI: OutOfMemoryError after repeatedly drilling down to Java profilers. (57043)

Workaround. Sometimes, when launching the profiler from the Enterprise UI, the entire UI (EUI,
profiler and Java console) will hang and, shortly thereafter, the profile and Java console windows
disappear and the remaining EUI window would not repaint. This problem can be eliminated by
upgrading the JRE used by the user's browser to a more current version of 1.6.

Can't restore chart after maximizing viewing "Chart Trends by Entity". (51105)

Workaround. Within the context of the chart view, the maximization and restore of frames does not work
correctly. If several charts were present they will no longer be visible. You can restore the chart view
by selecting a different metric grouping or by resetting the view layout.

NPE when loading System Health. (57363)

Workaround. Open a new browser or you can use the new System Health view group available in the
Enterprise UI.

Prior to exporting an Application Explorer view to html you should examine all of the tabs to activate the
population to the desired charts, otherwise the exported chart could be empty. (28801)

Navigation menu items on the popup (context) menu are different when right-clicked alone vs. selected
and then right-clicked. This occurs because only limited information is available when the first right-
click on an entity occurs, and the context menu is populated with what is known at that time. However,
the right-click operation immediately kicks off a query to the Diagnostics Server to find out more about
this entity, and so subsequent right-click operations use the returned data and the popup menu includes
more options. (29253)

In a custom 2-way view, both of the Navigation controls are updated with the navigations for the
selected entity. (29097)

When an application is selected (Application Explorer view) or a Probe Group is selected (Server
Summary view) you may see two "View Probe" navigations. This will happen when the Application or
Probe Group contains both .Net and Java Probes. (26471)

The navigation control only tracks the global time control. (29268)

Drilling from some alerts to "View Threshold Violation" results in a view that is empty except for the
message "Either no data is available for the selected time range, or the data at this level of detail has
been purged from the database."

This generally happens when the violating entity is 2 levels below the alert entity. For example, a probe
group alert from a server request threshold or a probe alert on a portal component--life cycle method
alert.

Workaround: Notice the breadcrumb of the empty view. This indicates the view that shows the data
causing threshold violation. Add the alert to a snapshot. From the snapshot, use the Navigations pane
to drill-down. In most cases, you would navigate to Probes first and the destination view below that.
For Life Cycle Methods, navigate to Portal Components (under Probes) first. For better navigation from
alerts to threshold violations, keep alert rules closer to the entities being monitored. (27612)

For server requests under 10 ms, Minimum Time will always be reported as zero. (34125)

Documentation

When the Diagnostics Server is installed on 64-bit Linux systems (only) the docs directory is not created
and so the manuals are not accessible from the <diagnostics_server_install_dir>/docs directory. Copies of
the pdf files can be found on the installation media and in the
<diagnostics_server_install_dir>/html/opal/docs/eng/help/pdfs directory. The manuals are also accessible
from the Diagnostics Online help.

If you experience a JavaScript error when opening the Diagnostics online help system, disable the "Show
Exceptions Dialog Box" in the Java Console and open the help again.

Environment

For an IPV6 environment, the following restrictions exist:

All Diagnostic Server, Collector, and Java Probe configuration must be based on host names (not
IP addresses).

.NET Probes are not supported.

Collectors must be running on IPV4 tunneled networks.

Linux and Solaris operating systems must be explicitly configured to use the IPV6
network host/IP resolution. On dual hosts, update /etcnsswitch.conf. On Solaris, update ipnodes

Translated Versions

Diagnostics has been translated into a number of languages. When using Diagnostics, occasionally text
that should be translated will be shown in English. This is due to limitations in third party components
that are used by Diagnostics. We apologize for any inconvenience that this might cause.

Support

You can visit the HP Software Support Web site at:

http://support.openview.hp.com/

This web site provides contact information and details about the products, services, and support that HP
Software offers.

HP Software online support provides an efficient way to access interactive technical support tools. As a
valued support customer, you can benefit by using the support site to:

Search for knowledge documents of interest

Submit and track support cases and enhancement requests

Download software patches

Manage support contracts

Look up HP support contacts

Review information about available services

Enter into discussions with other software customers

Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a
support contract. To find more information about access levels, go to:
http://h20230.www2.hp.com/new_access_levels.jsp

To register for an HP Passport ID, go to:
http://h20229.www2.hp.com/passport-registration.html

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent
with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and
Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard
commercial license.

The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an additional
warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

For information about open source and third-party license agreements, see the Documentation directory on
the product installation media.

Java™ is a registered trademark of Oracle and/or its affiliates.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Oracle® is a registered trademark of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

If you have any comments or suggestions regarding this document, please send them by e-mail to
SW-Doc@hp.com.