Page tree
Skip to end of metadata
Go to start of metadata

This section contains information about enhancements in version 9.0.30 of the BMC PATROL for Web URL KM.

What's new

The following new features have been introduced in this release of PATROL for Web URL KM:

New parameter to display 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 WUM_URL application class.

Backslash character supported in the instance name

RFE ID: QM001937960

Backslash character ( \ ) is now supported in the instance name. With this functionality, the instance name can be similar to the monitored Web URL. 

What's changed

The following features have been changed in version 9.0.30 of the PATROL for Web URL KM.

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: