9.0.30: Service Pack 3

Added Playback button to play recorded Web transactions

RFE ID: QM001879939

A new button has been added to the Web Capture screen to play the transactions from the Web recorder. You can use this option to validate a transaction file before adding it to the configuration. For information about how to use the Playback option, see Web Transaction Capture screen field descriptions.

Automatic deployment of Web transaction files to the PATROL Agents

Two new options, Add selected transactions for monitoring and Modify default configuration monitoring settings, are introduced in the Options menu of the Web Capture utility.

The Add selected transactions for monitoring option has been added to the Web Capture utility to deploy the web transaction files locally on the PATROL Agent that is running the TrueSight policy. This option enables you to connect to the TrueSight server and select the policies on which you want to deploy the Web Transaction files. You can also choose the transaction files that you want to distribute to the selected policies and the respective PATROL Agents.

The Modify default configuration monitoring settings option allows you to modify the default configuration settings of the transaction file. 

For information about how to use this option, see Web Transaction Capture screen field descriptions.

New parameter to address the content match result

A new parameter, Content match has been introduced to alert users if the content match results in a positive or negative match in the configured Web URL page content. This parameter is available in the WTX_Transaction application class.

Functionality changes in the Availability parameter

The Availability parameter now reports only the availability status of the monitored Web URL. However, it does not alert the users about the content match results. These alerts are reported by the Content match parameter. 

SSLv3 protocol disabled by default in JDK 8u31 onwards

To address the security vulnerability CVE-2014-3566, commonly known as Poodle, Oracle has disabled Secure Socket Layer (SSL) v3.0 by default in Java SE Development Kit 8, Update 31 (JDK 8u31) onwards.

BMC recommends that you do not use SSLv3. If you have an absolute requirement to use SSLv3, use the following options:

• Do not upgrade to JDK 8u31 or later. Earlier versions of JDK support SSLv3.
• If you have upgraded to JDK 8u31 or later, manually reactivate SSLv3.

To manually reactivate SSLv3

From the <JRE_HOME>/lib/security/java.security file, remove SSLv3 from the jdk.tls.disabledAlgorithms property or dynamically set the Security property to true before the JSSE is initialized.

For more information, see the following Oracle documentation:

• http://www.oracle.com/technetwork/java/javase/8u31-relnotes-2389094.html
• http://www.oracle.com/technetwork/topics/security/poodlecve-2014-3566-2339408.html