TransactionVision 9.02 Readme

for the Windows and Linux operating systems

Software version: 9.02

Publication date: March 2011

This file provides information about TransactionVision 9.02:

About this Release of TransactionVision

Documentation Updates

What’s New

System Requirements

Notes and Limitations

Support Matrixes

HP Software Support

Legal Notices

About this Release of TransactionVision

This release of TransactionVision is independent from HP Business Service Management (BSM),  and is compatible only with BSM version 9.01.  It also includes the latest hot fix release of the Java and .NET Agents.

This release includes the following components:

·         Transaction Management BSM UI updates;  file name:

·         TransactionVision Processing Server;  file names: HPTVProcServer_9.02_win.exe, HPTVProcServer_9.02_linux.tgz

·         TransactionVision Java Agent;  file names: HPDiagTVJavaAgt_9.01.20.203_win.exe, HPDiagTVJavaAgt_9.01.20.203_aix.bin, HPDiagTVJavaAgt_9.01.20.203_linux.bin, HPDiagTVJavaAgt_9.01.20.203_hppa.bin, HPDiagTVJavaAgt_9.01.20.203_sol.bin, HPDiagTVJavaAgt_9.01.20.203_hpia.bin, HPDiagTVJavaAgt_9.01.20.203_unix.tgz, HPDiagTVJavaAgt_9.01.20.203_zos.tgz

·         TransactionVision .NET Agent;  file names: HPDiagTV.NetAgt_9.01.20.36938_win32.msi, HPDiagTV.NetAgt_9.01.20.36938_win64.msi

·         TransactionVision WMQ Agent;  file name: HPTVWMQAgent_9.02_win.exe

·         TransactionVision z/OS Agent; file names,

For information about how to access and install these components, see the TransactionVision Deployment Guide.

Documentation Updates

The TransactionVision documentation in the BSM documentation library is updated when the Transaction Management BSM UI updates component is installed.

To check for recent updates or to verify that you are using the most recent edition, visit this URL (requires HP Passport credentials): HP Software Product Manuals

To retrieve a document, select the:

1.     Product name.

2.     Version list.

3.     Operating System.

4.     Preferred Language.

5.     Document title.

6.     Click Open or Download.

You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.

What’s New

This release contains the following enhancements to TransactionVision:

·         New DataPower Agent (first release with full DataPower support)

·         Java Agent rule-based custom data extraction

·         Java Agent expanded platform support for Tomcat 5.5 & 6.0 and JBoss 5.1

·         Java Agent support of Oracle WebLogic Server 11g

·         Processing Server and Java Agent support for VMware ESX Server 4

·         New utility to assist with correlation configuration

·         Many defect fixes

System Requirements

To view a complete list of system requirements for the TransactionVision components, see the TransactionVision Deployment Guide.

Notes and Limitations

These notes and limitations are specific to TransactionVision.  For general BSM notes and limitations, see the BSM readme that corresponds to your version of BSM.

Notes and Limitations Added for Release 9.02

·         Upgrading the Java and .NET Agents. The instructions for upgrading the Diagnostics/TransactionVision Java and .NET Agents in the “Upgrading TransactionVision” chapter of  the TransactionVision Deployment Guide are for upgrading an earlier version to a newer version. Alternatively, you can also uninstall the earlier version, remove its installation directory, and install the newer version instead.

·         The following error sometimes appears when accessing the Transaction Management > Administration page: Unable to communicate with BSM.

Workaround: Log out of BSM and log back in, and then access the Transaction Management Administration page again. (QCCR1I50435)

·         The Export command on all Transaction Management reports and topologies is not supported in this version. (QCCR1I50730)

·          Installation of the Processing Server on Linux typically is done by the “root” user. However you can run the installation as another user, allowing that user to own all log files and the Derby database.  

Change the following steps in Installing the Processing Server on Linux:

6 Type 1 and press Enter.


The following prompt will be displayed:

Please enter the user name to use for running TransactionVision processes [root]:


7 If it is desired to run the Processing Server as a different user than root, enter that user name.  Note, this sets appropriate permissions on the installed files and sets the RUN_AS_USER option in


The installation script installs the package, and displays the following messages:


Package tvision-sonicmq was successfully installed

Package tvision-analyzer was successfully installed


The TransactionVision component menu is displayed.


8 Type q and press Enter to quit the installation process.


9 Run <TVISION_HOME>/bin/run_topaz 'start' to start the Processing Server.


·         The Java Agent installation is missing the sonic_Crypto.jar and jsafe.jar files.

Workaround: Perform the following steps to support SonicMQ SSL connections in the Java Agent:

1 Copy sonic_Crypto.jar and jsafe.jar from <Processing Server Installation Directory>/Sonic/MQ7.6/lib to <Java Agent Installation Directory>/TransactionVisionAgent/integrations/OOBSonic.

2 Edit <Java Agent Installation Directory>/DiagnosticsAgent/etc/ and add sonic_Crypto.jar and jsafe.jar to probeTransportLoadPath. (QCCR1I56864)

·         Java Agent fails to send events on Tomcat 6.0 with WMQ 7.0.

Workaround: In situations where WebSphere MQ JMS is monitored for non-WebSphere Application Server (WAS) environments, you might see ClassNotFound errors for javax.jms.Exception and/or  

For the javax.jms.Exception ClassNotFound issue, modify the appSensorLoadPath property in the <JavaAgentInstallPath>/DiagnosticsAgent/etc/ file and add a fully qualified path to a jms.jar file. For example:
appSensorLoadPath=C:/Program Files/IBM/WebSphere MQ/java/lib/jms.jar;...

For the ClassNotFound issue, modify the appSensorLoadPath property in the <JavaAgentInstallPath>/DiagnosticsAgent/etc/ file and add a fully qualified path to the and files. For example: appSensorLoadPath=C:/Program Files/IBM/WebSphere MQ/java/lib/;C:/Program Files/IBM/WebSphere MQ/java/lib/;… (QCCR1I57331)

·         Null Pointer exception is seen in Admin > Transaction Management > Configuration tab (in the left panel) right after BSM login.

Workaround: Click the Refresh button on the Configuration user interface. Use JRE 6.0 update 24 for all Windows platforms if this issue occurs, using these steps:

1 Uninstall existing JRE version used in the browser.

2 Download and install JRE 1.6 updated 24 from

3 Restart the browser and launch BSM. (QCCR1I57212)

·         On the Status tab of the Processing Servers Summary and Processing Server page, repeated expand (+) and collapse(-) operations  can disable those controls.

Workaround: Click the Refresh button in the upper left portion of the page to restore the controls. (QCCR150530)

·         DataCollectionFilter.xml and PresentationQuery.xml need to be manually updated for the 9.02 release. Perform the following steps:

1 To allow filtering on user data, the following two sections must be added to DataCollectionFilter.xml (in the top-level TVision configuration tab / General):

<TechnologyCategory name="Servlet" icon="images/topaz/images/gui/mam_images/gui/images/classes/icons/body/app/app_16.gif">       

    <Group name="Servlet">


        <Category name="UserDataMatching" subname="UserData" desc="User Data" type="userData" view="">







<TechnologyCategory name="JMS" icon="images/topaz/images/gui/mam_images/gui/images/classes/icons/body/app/app_16.gif">
   <Group name="JMS">


        <Category name="UserDataMatching" subname="UserData" desc="User Data" type="userData" view="">





2 To allow querying on the user event service, the following section in PresentationQuery.xml (available in the same place) must be updated:


    <Category name="UserEventServices" type="object" objectType="8003" view="">


    <Category name="UserEventServices" type="object" objectType="8003" view="">
    </Category> (QCCR1I57746)

·         There are known problems with the way the Analyzer puts failed UserEvents and DataPower events to the exception queue.  Such events put to the exception queue will be corrupted and cannot be reprocessed by the Analyzer by transferring them back to the event queue using ManageQueue.  There is also a known defect in the Analyzer that prevents it from processing DataPower events that are put on the event queue using ManageQueue. Contact Hewlett-Packard Support if these defects have a major impact in the way you use TransactionVision. (QCCR1I57706, QCCR1I57711)

·         There is a known potential issue in TransactionVision that may cause the publishing of RTSM infrastructure CI relationships to Business Transaction CIs to fail.

Symptom: Errors like the following may occur in the jobmanager.log file:

2011-03-09 10:19:30,267 [JobThread-ODBPopulationJob] ERROR AppLog  - TransactionVision Error(AddCIFailed): Unable to add CI in RTSM: BTRelationshipCIData[302,120]
2011-03-09 10:19:30,267 [JobThread-ODBPopulationJob] ERROR AppLog  - TransactionVision Error(SystemModelMissingCIAttributes): Data required to populate CI not present in system model: BTRelationshipCIData[302,120]
2011-03-09 10:19:30,267 [JobThread-ODBPopulationJob] ERROR AppLog  - com.bristol.tvision.integrations.ucmdb.CMDBPopulationException
                at com.bristol.tvision.integrations.ucmdb.cidata.BTRelationshipCIData.addRelations(
                at com.bristol.tvision.integrations.ucmdb.InfrastructureCMDBService.syncInfrastructure(
                at com.bristol.tvision.integrations.ucmdb.CmdbAccess.syncInfrastructure(

Workaround: If such errors occur, it may be an indication of this known issue, and the following workaround will fix the problem.

1 Query for the System Model Business Transaction names within the Processing Server's database:


2 If any of the names in the result are "Invalid", you are experiencing the known issue.  Continue with the workaround steps.

3 Delete all System Model Business Transaction objects with the name "Invalid" from the Processing Server's database:


4 The Analyzer will automatically recreate these System Model Objects with the proper name when a new event is processed and classified under that Business Transaction.  After this occurs, RTSM Publishing should be corrected. (QCCR1I57792)

·         TransactionVision Administration pages may fail to initialize.

In some cases, the Admin > TransactionVision pages may not initialize. Errors such as the following appear:

java.lang.RuntimeException: java.lang.reflect.InvocationTargetException

              at sun.plugin2.applet.Plugin2ClassLoader.defineClassHelper(Unknown Source)

              at sun.plugin2.applet.Plugin2ClassLoader.access$100(Unknown Source)


Caused by: java.lang.NullPointerException

              at Source)

These errors are related to the Java Plug-in that is being used to view applets.  See

Workaround:  Use Version 6 Update 18 of the Java Plug-in. See the BSM Deployment Guide for information about the supported versions of the Java Plug-in.

·         WebSphere MQ Agent on UNIX produces many warnings in syslog.

On supported UNIX platforms, when using the WebSphere MQ Library Agent with client applications using a client channel definition table, the agent may produce repetitive warnings in the configured TransactionVision syslog file.

Workaround:  If this is problematic, syslog will have to be configured to not log from the TransactionVision WebSphere MQ Agent. (QCCR1I57316)

Notes and Limitations Carried Forward from Version 9.00/9.01

·         In rare cases, the Transaction Management > Administration page does not refresh correctly after some action and the following error appears: An internal error occurred. Workaround: Navigate away from the Transaction Management Admin UI page (by going to the site map or some other page), then return to it. The page should be correctly populated. (QCCR1I47950)

·         Significant efforts have been made to minimize CICS resource overhead of TransactionVision CICS and WMQ CICS Agents. However additional configuration steps have been identified which further reduce overall resource consumption of TransactionVision components that are part of the SLD architecture.  These steps are detailed in Chapter 15 of the TransactionVision Deployment Guide:  z/OS Components-Operation and Customization - Guidelines for Efficient Operation of Agent and Agent Manager Components. (QCCR1I34618)

·         On Linux hosts, the WebSphere MQ API Exit Agent unintentionally collects MQ Explorer events. Workaround: Add the following line to the <sensor_install_directory>/wmq_exit_agent.deny file:  /mqm/eclipse (QCCR1I48689)

·         When using BPI-TV integration, do not include attributes of type Decimal either when creating a customized data definition in the UI or when creating XDM definitions through imported XML.  Use Double instead of Decimal. (QCCR1I50361)

·         FIXED in 9.02. Logging may not function correctly after installing the 9.01 patch over previously configured (for 9.0) TransactionVision Processing Servers or Analyzers. Workaround: Perform the following procedure: 

For each Processing Server make the below changes. These changes are made on the Processing Server > Configuration tab > XML Configuration tab.

 In Job Manager Logging:

o    Change the priority value to warn:

 <priority value="warn"/>
<appender-ref ref="JOBMGR_LOGFILE"/>

o    Add this category:

 <!-- LW-SSO Log -->
<category additivity="false" class="com.bristol.tvision.util.log.XCategory"
name="" >
<priority value="info"/>
<appender-ref ref="JOBMGR_LOGFILE"/>

o    Replace all with org.apache.log4j.  You can press CTRL-R to perform a batch replace.

o    Click Apply to save your changes.

 In Query Engine Logging:

o    Change the priority value to warn:

<priority value="warn"/>
<appender-ref ref="JOBMGR_LOGFILE"/>

o     Add this category:

 <!-- LW-SSO Log -->
<category additivity="false" class="com.bristol.tvision.util.log.XCategory" name="" >
<priority value="info"/>
<appender-ref ref="QUERYENGINE_LOGFILE"/>

o    Replace all with org.apache.log4j.  You can press CTRL-R to perform a batch replace.

o    Click Apply to save your changes.

 For each Analyzer, make the below changes. These changes are made on the Processing Server > Analyzer > Configuration tab > XML tab.

In Analyzer.Logging:

o    Add this category:

<!-- LW-SSO Log -->
<category additivity="false" class="com.bristol.tvision.util.log.XCategory" name="" >
<priority value="info"/>
<appender-ref ref="ANALYZER_LOGFILE"/>

o     Replace all with org.apache.log4j.  You can press CTRL-R to perform a batch replace.

o    Click Apply to save your changes

·         The Transaction Tracing Rules Configuration page and Rule Creation wizard have an advanced parameters area. The "Attribute evaluation occurs within classify section" option on in this area is working incorrectly.  Setting this should include the rule in the classify section, and vice versa, but it does not.  Workaround: Use the opposite settings: To include a rule in the classify section, set the option to off.  Conversely, to put a rule outside classify section, set the option to On. (QCCR1I47857)

·         WMQ Batch z/OS Agents cannot be terminated by using the /F TVISION,STOP MQBATCH command when TVISION Manager is shared among different z/OS Agents. Workaround:  Customer could start multiple TVISION Manager components, one for just the WMQ-BATCH agent, and the other for all other types of agents.  This would allow the WMQ-Batch agent to be brought down gracefully, by issuing a stop command to its TVISION Manager independent of the other TVISION Manager and its agents. (QCCR1I47690)

·         There is very limited support for the new WebSphere MQ 7.0 Publish/Subscribe feature.  As part of this limitation, MQPUT and MQGET API using topics will not be correlated. (QCCR1I45059)

·         The TransactionVision Advanced Customization Guide is not fully updated with respect to the new 9.00 TransactionVision APIs. Please check for an update to this manual on the HP Software Product Manuals site.

·         Functionality of the TransactionVision WMQ CICS Agent Version 9.00 is adversely affected by IBM APAR PK70901 for IBM CICS Transaction Server V3.2.  Please check the maintenance level of your CICSTS32 system to see if APAR PK70901 has been applied.  If so, please contact Hewlett Packard Technical Support for further assistance before enabling the WMQ CICS Agent V9.00 within your CICSTS32 environment(s).   (QCCR1I38314)

·         The User Reports feature available in TransactionVision 8.0 is not available in 9.00. (QCCR1I41146)

·         When running TransactionVision components together with Business Service Management and/or Business Process Insight and/or Diagnostics, all software versions must be the same - for example if running Transaction Management from Business Service Management 9.00, installed TransactionVision components must be version 9.00, Business Process Insight (if installed) must be 9.00, and Diagnostics (if installed) must be 9.00.

·         On WebLogic application server platforms, in rare scenarios, it is possible that some transactions have abnormal transaction duration time due to the JMS API acknowledge calls that take many minutes to complete. Solution: Change the Data Collection filter of your Communication Links to filter out these JMS acknowledge events.

·         The following information applies to customers installing TV 9.0x agents on z/OS that do not have either CICS or IMS installed on the target z/OS system. 

In general, the intent of this modification is to create and make available dummy interface modules for IMS and/or CICS by assembling and linking them into the TransactionVision SSLDLOAD library and then make all references to the SDFHLOAD (CICS) or SDFSRESL (IMS) libraries refer to the TV SSLDLOAD library.

Select one of the following dependent on the type of install.

SMP/E Installation:

o    Within installation JCL member SLDDDDEF, adjust the %cicshlq and %imshlq substitution values and suffix constants .SDFHLOAD and .SDFSRESL respectively, replacing these values and constants as necessary to generate the dataset name produced by the concatenation %tvhlq..SSLDLOAD. 

o    Immediately preceding the execution of JCL member SLDDDDEF, execute JCL members DUMYCICS and DUMYIMS as needed (if for example CICS is installed, but IMS is not, then only execute DUMYIMS).  Load modules output from either of the DUMY* jobs need to target the library %tvhlq..SSLDLOAD.  Also, if DUMYIMS is being used, please insert the following two lines immediately after the line starting with '//L.SYSLMOD  DD ':

//L.SYSIN    DD *

Execute JCL member SLDDDDEF containing the above modifications.

Repeat the steps above when performing SMP/E installation of the SLM product code, tailoring SLMDDDEF, and substituting SLM for SLD as necessary.

Non-SMP/E Installation:

o    Within installation JCL member SLDINSTL, after the DEFINE step, insert JCL members DUMYIMS and DUMYCICS as needed (if for example CICS is installed, but IMS is not, then only insert DUMYIMS). Tailor the DUMY* JCL member(s) to output load modules targeting library %tvhlq..SSLDLOAD.  Also, if DUMYIMS is being used, please insert the following two lines immediately after the line starting with '//L.SYSLMOD  DD ': 

o    //L.SYSIN    DD *                                                     
ALIAS   DFSLI000                                                    

o    Within installation JCL member SLDINSTL, after the DEFINE step, insert JCL members DUMYIMS and DUMYCICS as needed (if for example CICS is installed, but IMS is not, then only insert DUMYIMS).  Tailor the inserted JCL to output load modules to target library %tvhlq..SDFHLOAD.

o    Tailor SLDINSTL replacing references to %cicshlq and %imshlq substitution values and suffix constants .SDFHLOAD and .SDFSRESL respectively, replacing these values and constants as necessary to generate the dataset name produced by the concatenation %tvhlq..SSLDLOAD. 

o    Execute JCL member SLDINSTL.

o    Repeat the above steps when performing non-SMP/E installation of the SLM product code, tailoring SLMINSTL, and substituting SLM for SLD as necessary.

·          Java Agent installation and Setup Module response files generated with version 8.00 cannot be used to perform a silent installation of the 9.0x version of the Java Agent installation and Setup Module. Response files generated with 8.01 and later will work with 9.0x releases.

·         The TransactionVision Processing Server is installed under /opt/HP/TransactionVision on Solaris and RedHat Enterprise Linux, and under /usr/lpp/HP/TransactionVision on AIX. While it is not possible to change the installation path, it is possible to create soft-links to ensure that the product files are placed on a drive or partition with available space. Under normal circumstances, customers may create a soft-link from /opt/HP/TransactionVision or /usr/lpp/HP/TransactionVision to a new location prior to running the installation script. However, due to a limitation in the SonicMQ installation with respect to soft-links, the SonicMQ files must be installed under the default /opt/HP/TransactionVision/Sonic or /usr/lpp/HP/TransactionVision/Sonic directory. If space is a concern, customers may still create soft-links for other higher capacity directories (such as jre, jre64, java, docs, and logs) under the TransactionVision installation directory.

·         On AIX systems, after the Java Agent installation, the following message will appear:

The Installation Wizard has successfully installed HP Diagnostics/TransactionVision Agent for Java.  Choose next to continue the wizard. 

However, on some systems, the following warning is also generated: o  null.

In this case, the installation has succeeded and the message can be ignored.

·         When starting HP Business Service Management on Solaris systems using the "run_topaz start" command, "Bad String" errors may be seen if the LANG environment variable is not set properly. These errors can be eliminated by setting LANG to the proper locale prior to starting BSM. For example, run the command "export LANG=en_US.UTF-8" to set LANG for U.S. English.

·         Customers who plan to enable the TransactionVision IMS sensor on z/OS should ensure that they are not already using the IMS OTMA Input/Output exit (DFSYIOE0) for some other non-TransactionVision purpose before proceeding with the IMS sensor configuration.  If DFSYIOE0 is already being used for customer internal purposes or by another vendor product, please contact TransactionVision customer support for detailed instructions on how to modify DFSYIOE0 source code to invoke the TransactionVision IMS sensor (SLMYIOE0).

·         Starting with z/OS version 1.9, the default setting for system parmlib DIAGnn member statement VSM ALLOWUSERKEYCSA has changed to "NO." This parameter disallows User Key CSA storage for security reasons. In order for TransactionVision 9.0x Agents to execute successfully under z/OS, the VSM ALLOWUSERKEYCSA parameter value must be set to "YES."

·         When using the Diagnostics/TransactionVision Agent to monitor WebLogic 9.2.2 and 9.2.3 on Linux, the following error may be seen due to a problem with the version of the JVM shipped with that version of WebLogic, which causes the server to not start:

<Dec 3, 2008 5:41:17 PM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NullPointerException


  at weblogic.t3.srvr.SubsystemRequest.action(

  at weblogic.t3.srvr.SubsystemRequest.start(

  at weblogic.t3.srvr.ServerServicesManager.startService(

  at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(

  at weblogic.t3.srvr.T3Srvr.initializeStandby(

  at weblogic.t3.srvr.T3Srvr.startup(


  at weblogic.Server.main(

To work around this problem, the following steps should be performed:

o    Edit the weblogicEJBCacheCollection.xml file under the directory MercuryDiagnostics/JavaAgent/TransactionVisionAgent/config/sensor/instrumentDef/Weblogic and remove the following section:

<ClassName name="">       

<Action name="ForwardMethodCall">

<SensorFlagName name="com.bristol.tvision.sensor.CheckSensor.servletSensorInstalled"/>

<SensorClass name="com.bristol.tvision.sensor.servlet.ServletSensor"/>

<SensorMethodPrefix name="DomainMBeanImpl_"/>

<MethodSignature name="void setName(java.lang.String)"/>



o    Edit the file under MercuryDiagnostics/JavaAgent/DiagnosticsAgent/etc directory to add the following at the end of the tvProperties line.


Note that the WebLogic domain name is usually the directory containing your server.

o    Restart your WebLogic server.

·         TransactionVision data is always saved to the default profile database in HP Business Service Management.

·         FIXED in 9.02. Successful execution of the TransactionVision V9.01 WMQ CICS Agent may require additional IBM CICS maintenance when running in CICS Transaction Server V3.2 or V4.1 environments:   

·         FIXED in 9.02. Processing Server installation does not complete on some Linux systems.  Workaround:  If during the Sonic 7.6.2 upgrade portion of the Processing Server installation on Linux the display appears to hang, press Crtl-C to continue the installation. (QCCR1I49235)

·         FIXED in 9.02. The Timeslice interval used for the Component Topology is not configurable in 9.01. The default of 60 minutes is always used.

·         FIXED in 9.02. Customers using the TransactionVision WMQ CICS Agent for z/OS need to relink module SLDPXADM as serially reusable instead of re-entrant in order to avoid an ASRA at location +x23C within module SLDPXADM, part of the WMQ CICS Administrative UI component .  The following JCL can be used for this purpose:


//*  Please make a copy of SLDPXADM before executing






//SYSIN    DD *





(CR QCCR1I47728)

·         FIXED in 9.02. A known issue exists for the TransactionVision product where the current license capacity “used" value is incorrectly displayed in the Capacity Details section of the License Management report. (QCCR1I47012)

·         FIXED in 9.02. Host consolidation in ODB is mismatched with respect to z/OS host names.  In order for proper host consolidation in ODB, the hostnames provided by TV events from z/OS agents need to be fully qualified domain names. (QCCR1I41816)

·         If modifying default Time Slice Delta and/or Sample Delta settings in the "BSM Aggregate TV Data Sample" job, the Collection Interval and Aggregation Delta settings in CIs need to be set to the same value respectively. This is required for proper functioning of CI status display in BSM Service Health.  (QCCR1I48216)

·         FIXED in 9.01. The default data collection filter section is incorrect in the Using Transaction Management Guide. The corrected section appears below.

The Default Filter

If no data collection filter is specified, then the default filter is used. This filter can be customized but has the following initial settings:

For WebSphere MQ: Only MQGET, MQPUT, and MQPUT1 API names are included. Do not send browsing MQGET is set.

For JMS: send, receive, receiveNoWait, publish, and onMessage methods are included.

For Servlet: only the first 1024 bytes of HTTP request and response data are included.

The JDBC technology is off.

For all technologies:  event packaging is enabled and the number of events to package is set to 10 events.

·         FIXED in 9.01. After making changes to an existing communication link and saving the changes, subsequent attempts to edit the communication link result in a "restClient failed" exception. Workaround: Either click the Refresh button on the main configuration tree or re-login to BSM. (QCCR1I47915)

·         FIXED in 9.01. The SQL Alerts custom job is not supported in this release. References to this feature in the documentation should be ignored. For example, the SQL job bean example shown in the TransactionVision Advanced Customization Guide will not work. (QCCR1I47859)

·         FIXED in 9.01. If the HP Business Service Management Servers are using an SSL configuration with client authentication, manual configuration of the TransactionVision Processing Servers is required as follows.

Set and properties by un-commenting and optionally updating (if not using default <TVISION_HOME>/jre/lib/security/cacerts as a keystore) the SSL_PROPERTIES variable in the <TVISION_HOME>/bin/set_env script on each TransactionVision Processing Server host. For example, below is the un-commented SSL_PROPERTIES variable in the unix script.$TVISION_HOME/jre/lib/security/cacerts

After modifying the file, restart all processing server components by using the SupervisorStop and SupervisorStart scripts. (QCCR1I45864)

·         FIXED in 9.01. If the TransactionVision content pack is deployed, duplicate entries might be observed in Admin>Service Health>Repositories, such as duplicate rules, context menus and actions. (QCCR1I47660)

·         FIXED in 9.01. You may see two EJB or servlet nodes in the Component Topology or Instance topology view that only differ in application server name. For example, one with a short name such as "server1" and the other with a long name such as "cell1,node1,server1". This is the result of some events that do not have full application server information. (QCCR1I47198)

·         FIXED in 9.01. Some of the "Correlation Measurement" metrics in the Transaction Over Time report's filter may not be applicable for Diagnostic Transactions. (QCCR1I47941)

·         FIXED in 9.01. A "Drill to Transaction Tracking Report" button will be enabled in the Transaction Over Time report even though there is no TransactionVision data present.  This button should be disabled. (QCCR1I47940)

·         FIXED in 9.01. In the Processing Server Configuration section of the Admin UI, the Sync Interval field does not display the units of the field, which are in minutes. (QCCR1I42973)

·         FIXED in 9.01. The Java Agent will continue to collect events even after Configuration Messages have expired or the Analyzer, SonicMQ or the TV database are not accessible. (QCCR1I47532)

·         FIXED in 9.01. The following drilldowns from TransactionVisions reports to End User Management reports do not work, and a No data was found error is displayed:

o    Transaction Tracking report drilldown to RUM End User Group Summary report

o    Transaction Summary report drilldown to RUM Transaction Summary report (QCCR1I48210)

Documentation Library

Refer to the PDF versions of all TransactionVision documentation for the most up-to-date information. The PDFs are available by clicking the PDF symbol for each manual  in the Transaction Management portal in the BSM Documentation Library, or by downloading them from HP Software Product Manuals.

The online help (HTML)  in the Transaction Management portal of the BSM Documentation Library does not contain information about the TransctionVision 9.02 features.

TransactionVision Support Matrixes

The following Compatibility Matrix supersedes the one in chapter 2 of the TransactionVision Deployment Guide.        


Versions of Agent Compatible with 9.02 Processing Server

Versions of Processing Server Compatible with 9.02 Agent

HP Diagnostics/TransactionVision Java Agent

8.0x, 9.00, 9.01


HP Diagnostics/TransactionVision .NET Agent

8.0x, 9.00, 9.01


WebSphere MQ Agent

8.0x, 9.00, 9.01, 9.02


DataPower Agent



CICS, WMQ Batch,

WMQ CICS, WMQ IMS, and IMS Bridge Agents on z/OS

8.0x, 9.00, 9.01, 9.02


BEA Tuxedo Agent

8.0x, 9.00


NonStop TMF Agent



1 If you require use of this 9.02 agent with an older Processing Server/Analyzer, contact HP TransactionVision Support for potential product compatibility/incompatibility details.

HP Software Support

You can visit the HP Software support web site at:

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

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

·         Search for knowledge documents of interest

·         Submit and track progress on support cases

·         Submit enhancement requests online

·         Download software patches

·         Manage a support contract

·         Look up HP support contacts

·         Review information about available services

·         Enter discussions with other software customers

·         Research and register for software training

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

Legal Notices

© Copyright 2005 - 2011 Hewlett-Packard Development Company, L.P.

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 third-party license agreements, see the Third_Party_Agreements directory on the product installation media.

For information about open source license agreements, see the Open_Source_Agreements directory on the product installation media.

Trademark Notices

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

AMD and the AMD Arrow symbol are trademarks of Advanced Micro Devices, Inc.

Google™ and Google Maps™ are trademarks of Google Inc.

Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.

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

Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.

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

UNIX® is a registered trademark of The Open Group.


This product includes software developed by the  Apache Software Foundation (

This product includes software developed by the JDOM Project (

This product includes software developed by the MX4J project (

If you have any comments or suggestions regarding this document, please send them by e-mail to