This topic contains information about fixes and updates in this service pack.
For information about issues corrected in this service pack, see Known and corrected issues.
Hash mapping disabled for instance names
In this release, the hash mapping for instance names is disabled by default in all the configured environments. With this enhancement, the complete path of the parameter is displayed in the PATROL Console. You can enable hash mapping for specific environments by using JVM arguments.
Consider the following to retain the environment history and to ensure a smooth upgrade from version 3.0.10 to version 3.1.00 of BMC PATROL for IBM WebSphere Application Server.
If you want to use hash code paths in the instance names, BMC recommends that you, as the database administrator, add the
-DlongInstanceMapping=false JVM argument to the respective environment. To add JVM arguments, perform the following step:
- Right-click the Environment name > KM commands > KM Administration > Define JVM Arguments option and enter the argument.
- Set the value to
/PMW/WebSphere/<<environment name>>/jvmArgspconfig variable
Support for WebSphere version 9
PATROL for IBM WebSphere Application Server is now supported for WebSphere version 9.
Filters for monitoring application classes
PATROL for IBM WebSphere Application Server introduces filters that you can use to include or exclude WebSphere Application Servers and instances from monitoring, based on the server and instance names.To configure the KM in the TrueSight console, see Configuring WebSphere Application Server using Central Monitoring Administration and ruleset file.
New platform support
PATROL for IBM WebSphere Application Server is now supported on for Red Hat Enterprise Linux 7.2 LE on IBM Power8.