IBM Support

Fix/Update list for IBM Business Monitor V7.5

Product Documentation


Abstract

IBM Business Monitor provides periodic fixes and updates for V7.5. The following is a complete listing of fixes for V7.5 with the most recent fix at the top.

Content

Version 7.5.1 Fix Pack 2


Version 7.5.1 Fix Pack 1
Version 7.5.1.0 Interim Fix JR42840
Version 7.5.1.0 Interim Fix JR41464
Version 7.5 Refresh Pack 1
Version 7.5 Fix Pack 1

Version 7.5.1 Fix Pack 2


Fix release date: 7 March 2014
Last modified: 7 March 2014
Status: Available (Recommended)

 

 

Download Version 7.5.1 Fix Pack 2

 

 

 

APAR
 Description
The “Show Instances” function from the Report Viewer widget to the Instances widget does not filter instances in the Instances widget based on prompts added to a report in Cognos Report Studio.
The “Show Instances” function from the KPI widget to the Instances widget does not display the correct set of instances in the Instances widget if the KPI does not have a data filter.
The group search in the Monitor Data Security panel of the WebSphere administrative console may fail to return groups.
DDL for enabling the Data Movement Service for DB2 does not export correctly from the WebSphere administrative console if the total width of all columns in the table is greater than 31,900 bytes.
Drilling down on a dimension in the Report Viewer widget fails for a string metric when there is a long dimension value and Oracle is the database.
If the Purge and Archive service runs with respect to a large set of instance data, then the purge operation performance is slow.
When searching in the Instances widget, an error is displayed if a value with a decimal point is entered to search for a decimal type metric.
Filtering the Instances widget on a date metric may display instances from a day prior to the specified date or date range.
There is a memory leak in the com.ibm.wbimonitor.router.scalable.distribution.MMRoutingClassLoader Common Event Infrastructure routing plugin that can lead to heap memory exhaustion.
An e-mail alert is not delivered if the corresponding e-mail address is mapped to multiple users in the configured user repository.
Instance data retrieval from the Instances widget can lead to heap memory exhaustion, especially when retrieving a large number of instances.
User removal from a dashboard alert subscription is not persistent and alerts continue to be sent to the user.
When scheduling a report in Cognos, selecting a link to create credentials may result in a “credentials are invalid” error that is presented in a pop-up window.
After choosing to export instances listed on all pages of the Instances widget, the complete set of instances is not exported.
A cached value for “hasXctIdColumn” can potentially cause event processing failures following monitor model deployment or undeployment.
When fine-grained security filters are applied and dashboard alerts are being used, there could be erroneous alerts or missing dashboard alerts because fine-grained security filters are not evaluated for KPIs when evaluating dashboard alerts.

 

 

Back to top

Version 7.5.1 Fix Pack 1


Fix release date: 25 September 2012
Last modified: 25 September 2012
Status: Available (Recommended)

 

 

 

Download Version 7.5.1 Fix Pack 1

 

 

 

APAR
 Description
Alphablox cubes cannot be edited in the Alphablox administrative console.
On AIX or HP-UX, when launching the configuration of Cognos Business Intelligence (for IBM Business Monitor), an error is written to SystemOut.log.
If the Dimensions or Reports widget is wired to the Instances widget, the Show Instances function does not display any instances.
On a server where Cognos Business Intelligence is running, a warning message is periodically written to the SystemOut.log file.
Using complex XPath expressions in diagrams which use "or" and "and" statements will result in warnings in the SystemOut.log file on the server or cluster where the monitor model is running.
When using the Instances widget, the localized timestamps used in the instances do not honor Daylight Savings Time. (Refer to this technote for details on configuring a custom property that defines a fixed time zone for display of all timestamps that honors Daylight Savings Time.)
Complex fine grain security filters, and repeated LDAP lookups, impact performance of IBM Business Monitor widgets.
Two issues in the Cognos Cache Clearing service need to be addressed:

1) Calling the Cognos Cache Clearing service in the Monitor admin page (Monitor Scheduled Services > [application] > Scheduled Services > Cognos Cache Clearing > Versions) always shows a failure message.
2) Cognos sessions initiated by the service (one per run) are not terminated, resulting in a "session leak".
The Show Instances function in the Cognos Report Viewer widget does not filter instances in the wired Instances widget based on filter defined in the Report Viewer widget.
When a user logs out of Business Space, after having accessed a Cognos related widget (e. g. Cognos Report Viewer) during the session, a Cognos authentication dialog may appear, forcing the user to log back in to Cognos before the logout can complete.
With an Instances widget and at least one other widget on the same page in Business Space, if a widget besides the Instances widget is in the maximized state at the time the page is loaded, the page fails to render properly.
An Alphablox API to support fine grained security for dimensional data does not exist in IBM Business Monitor Version 7.5.1.
The KPI Manager widget cannot be used to create an aggregate KPI based on a metric in an nested monitoring context.
If IBM Business Monitor must access the Cognos server via an HTTP server, Cognos cache clearing via the administrative console fails.

 

 

Back to top

Version 7.5.1.0 Interim Fix JR42840


Fix release date: 30 July 2012
Last modified: 30 July 2012
Status: Available

 

 

 

Download Version 7.5.1.0 Interim Fix JR42840

 

 

 

APAR
 Description
Two issues in the Cognos Cache Clearing service need to be addressed:

1) Calling the Cognos Cache Clearing service in the Monitor admin page (Monitor Scheduled Services > [application] > Scheduled Services > Cognos Cache Clearing > Versions) always shows a failure message.
2) Cognos sessions initiated by the service (one per run) are not terminated, resulting in a "session leak".

 

 

 

Version 7.5.1.0 Interim Fix JR41464


Fix release date: 7 March 2012
Last modified: 7 March 2012
Status: Available

 

 

 

Download Version 7.5.1.0 Interim Fix JR41464

 

 

 

APAR
 Description
On AIX or HP-UX, when launching the configuration of Cognos Business Intelligence (for IBM Business Monitor), an error is written to SystemOut.log.
On a server where Cognos Business Intelligence is running, a warning message is periodically written to the SystemOut.log file.

 

 

Back to top

Version 7.5 Refresh Pack 1


Fix release date: 18 November 2011
Last modified: 18 November 2011
Status: Available (Recommended)

 

 

Download Version 7.5 Refresh Pack 1

 

 

APAR
 Description
Multiple improvements are needed for robustness, performance, and usability of failed event management, including resubmission.
The KPI History And Prediction widget does not work correctly when no internet connection is available.
On UNIX systems, the database creation phase of profile creation or augmentation with IBM Business Monitor fails when the name of the user who initiated the operation is the proper prefix of another user name (in the /etc/passwd file); for example, "user1" and "user10".
For an expression KPI whose expression is based on a user defined function or an XPath expression referencing the current date or time, history calculation does not work.
In the Human Task widget, the first time you set a "fuzzy" filter or string filter and save it, the filter works correctly; however, editing the filter again and saving it results in failure of the filter, with no instances displayed in the widget.
During profile creation or augmentation with IBM Business Monitor, where Cognos BI is not installed in <WAS_HOME>/cognos, generation of the Cognos BI EAR file will fail (with a non-fatal error) in the file <PROFILE_NAME>_create.log or <PROFILE_NAME>_augment.log.
In the WebSphere test environment, during startup of the default Process Server profile qwps (with no IBM Business Monitor), the Monitor class com.ibm.wbimonitor.repository.DBDataSource.getConnection is loaded, and it fails with error ClassNotFoundException:
COM.ibm.db2.jdbc.app.DB2Driver.
When using the moveMCInstances method to move active instances from an older monitor model version to a newer version, and the newer version introduces a new cube with a new date dimension, the method fails with an SQL exception for any instance in the older model version with a null value for the metric upon which the new dimension is based.
When the Purge and Archive service is executed against a large set of instance data, the purge operation may cause an out of memory condition on the JVM on which the service is running.
With the Data Movement Service enabled for a monitor model, the Purge and Archive service (configured with a filter to select instances based on when they were terminated) performs slowly, especially with a large number of instances in the TGT tables for the monitoring contexts associated with the model.
The IBM Business Monitor REST services plug-in is not packaged correctly for interoperability with WebSphere Process Server V7.0 and higher . As a result, actions in the Human Tasks widget which invoke Business Process Choreographer (such as "Transfer to another user") fail.
The following internally identified issues have been resolved:

Issues in monitor model installation/uninstallation:
  • Deployment of a large monitor model may fail due to a hung thread.
  • For a development mode server, events are not removed from the failed event queue when the last version of a model is uninstalled or purged.
  • Uninstalling one of multiple versions of a model deployed from the Process Designer (in Business Process Manager) may cause the Instances widget to generate an SQL error in SystemOut.log.
  • Monitor model auto-generation from Process Designer fails with security enabled.
  • With SQL Server (with enhanced security) as the database, the "create schema" script for a monitor model does not contain the proper GRANT statement for monitoring context (MCT_*) tables, causing widgets configured for the model to fail.
  • When deploying a snapshot of a process application with monitoring from Process Center (in Business Process Manager) to a network deployment environment (with BPM Advanced and Monitor in the same profile), process/model versioning issues may surface later (as indicated by CWMLC2514E messages written to SystemOut.log during the initial snapshot deployment).
  • A monitor model generated from a Process Center snapshot does not properly deploy to a four-cluster environment.

Operational issues:
  • Some events emitted by the Global Process model do not contain a hierarchy instance ID, causing them to be routed to the unrecoverable event queue.
  • When an event is imported and it fails during processing, the failure time of the event (in the failed event queue) is set to the time the event was imported, not the time the event failed.
  • A failed event cannot be resubmitted to a different version of the monitor model in which it failed.

Issues in Cognos functionality:
  • The first time a Report Viewer widget is loaded (after initial configuration), if the load takes more than 30 seconds, there is no visible sign of activity.
  • In the Report Viewer widget, the Show Instances function does not filter based on all dimension levels, only the current level.
  • In the Report Viewer widget, a report that is not based on a monitor model cannot be viewed.
  • In WebSphere Portal, with Internet Explorer 7 as the browser, the Report Viewer widget scrollbars do not work correctly.
  • If a monitoring context name matches the model name, Cognos cube creation for that monitoring context fails.
  • If a monitoring context name contains special characters, Cognos report creation fails.
  • The Cognos Cache Clearing scheduled service does not clear the cache for cross-version cubes when set to "Run Now".

Issues in fine grain security:
  • A user with the 'Public KPI Administrator' role can see the target and ranges of KPIs with security filters, that the user does not own.
  • Cognos fine grain security does not work properly with subgroup users.

Issues in the administrative console:
  • For a monitor model deployed from Process Designer, the Tuning tab in the monitor model runtime configuration page is greyed out.
  • No default value is displayed for the Late arrival stand off delay property in the monitor model runtime configuration page.
  • A resource group name with special characters is incorrectly formatted in the Monitor data security page.
  • A Monitor data security resource group name with special characters causes the link in the Monitor models page that should be labeled "No members assigned" to be corrupt (label is incorrect and link does not work).

Issues in the IBM Business Monitor widgets:
  • Wiring between the Instances widget and Business Process Manager widgets does not work correctly (the error ""No system ID specified, this is required for a federated backend!" is thrown when the Instances widget sends an event to a BPM widget).
  • In the Instances widget, setting a data filter using the "in" operator throws an error.
  • In the Instances widget, if the application for a version of a monitor model has been uninstalled, but the schema has not been deleted for that version, clicking "Include model specific versions" throws an error and no version can be selected.
  • In the KPI widget, a KPI which should be hidden from a user by fine grain security appears with a "Retrieval error".
  • When editing the Diagrams widget, selecting a KPI context diagram when a monitoring context diagram is currently selected does not work the first time (KPI context changes to "No Selection" and the desired value must be selected again).
  • In the Dimensions and Reports widgets, a saved bookmark disappears after switching back and forth between Business Space pages.
  • In the mobile dashboard, in the KPI and Alerts widgets, the button at the top left does not scroll properly.

Other issues:
  • Stopwatch values are incorrect after instance data import.
  • After the showcase model is installed, the Business Alerts space does not contain the Instances widget (Active Loans).

 

 

Back to top

Version 7.5 Fix Pack 1


Fix release date: 9 August 2011
Last modified: 9 August 2011
Status: Available (Recommended)

 

 

 

Download Version 7.5 Fix Pack 1

 

 

 

APAR
 Description
In the Dimensions and Reports widgets, after certain customizations are made to specific measures and then the Save Format button is clicked to save the customizations, the customizations are not properly restored the next time the widget is loaded or refreshed.
The "updateMMApplicationLibraries" script will fail with a ClassNotFoundException if the Monitor installation path contains any spaces.
When migrating from an older version to Version 7.0, the profile migration script overwrites files in the "lib" directory under the Alphablox installation directory in the newer version with files from the older version (if the older version is active and if Alphablox is installed in the directory
<Monitor_root>/Alphablox for each version, respectively).
When the "create schema" script for a monitor model is exported via the administrative console, the script file that is generated contains comments in two locations that imply that the statements that follow them are applicable to V6.2 only.
An SQL query executed by Monitor to determine which monitoring context instances are due to have a time based trigger evaluated contains an unnecessary sort, impacting overall event throughput, especially if there are a large number of open monitoring context instances.
When using the WebSphere deployment environment wizard, the WebSphere shared libraries for Alphablox are created at the cell scope, resulting in startup errors on nodes in the cell where Alphablox is not installed.
The following internally identified issues have been resolved:

Issues in monitor model installation/uninstallation:
  • In a cross cell configuration, uninstalling a monitor model using queue bypass fails to remove the event group for the model from the remote CEI server.
  • After uninstalling a monitor model without deleting the schema, clicking "Change runtime configuration" in the model version page in the administrative console results in "error 500" being thrown.
  • Installing a monitor model leaves a directory "mmdeploy" in a temporary directory, with roughly 35MB of files. These should be removed when installation is complete.
  • For a monitor model automatically generated and deployed from Process Designer ("Update tracking definitions" action), the user cannot view the model in the generated Business Space.
  • In a monitor model deployed by the "Update Tracking Definitions" action in Process Designer, event reordering is not enabled by default.
  • On 64-bit Windows 7, the showcase model fails to install.

Operational issues:
  • Alphablox may not start correctly on server/cluster startup due to a timing issue.
  • With SQL Server as the database, processing of DateTime metrics in the Global Process Monitor model may fail due to an SQLServerException.
  • For fine grained security, validation of an imported filter rule performs case insensitive matching of the monitoring context ID the import file to the actual ID, resulting in incorrect import and failure to correctly apply the filter rule.
  • For fine grained security, no validation error is reported during import of a filter rule if FilterOperator is excluded from a filter.
  • With tracing of com.ibm.wbimonitor,actionmgr enabled, e-mail alert notification generates an unnecessary SMTP exception in the trace if none of the targeted users have e-mail addresses (in the LDAP or federated repository).
  • On Windows 7 64-bit, the Installation Verification Tool fails (no output).
  • In the Installation Verification Tool, the showcase model verification fails.

Issues in Cognos:
  • If an incorrect URL (or user name or password) is configured for a remote Cognos service, the "Manage Cognos cube package" panel does not show an error message indicating the issue.
  • In the Configure IBM Cognos Service panel, no validation error is reported if the user name or password is incorrect for a remote Cognos service.
  • Running AdminTask.wbmSetCognosDispatcher to set the Cognos dispatcher URI corrupts the Cognos widget endpoints.
  • The Cognos service to clear the cache fails (with the error message "CWMDS5901E: Failed to run the Cognos task to clear cache..." written to SystemOut.log).
  • Cognos security filtering does not properly evaluate all values of an LDAP attribute that is an array of values.
  • On Oracle, if the Oracle SID and Oracle global database name are different, the Cognos connection to the database will fail.
  • In a Cognos environment with cubes from IBM Business Process Manager and WebSphere Lombardi Edition models, if a monitoring context from a BPM model has the same name as a monitoring context from a WLE model, a Cognos namespace collision will occur.
  • In a network deployment environment, after updating Cognos BI with a fix bundle, the Cognos service fails to start, with the error "The handler class 'com.ibm.wbmimonitor.security.cognos.auth.VMMProvider' cannot be loaded" written to the Cognos log.

Issues in profile management:
  • The WebSphere Application Server administrative password is exposed in profile augmentation logs.
  • The Monitor and Cognos database passwords are exposed in the augmentation log when a profile is augmented with Monitor.

Issues in the administrative console:
  • When using remote Cognos, the "IBM Cognos Connection web client" link in the Manage Cognos cubes page is incorrect.
  • The "Documentation" link in the administrative console points to the Version 7.0 Information Center instead of Version 7.5

Issues in the WebSphere Business Monitor widgets:
  • In the Alert Manager widget, if a dashboard alert is marked invalid because it is supposed to fire at the end of a KPI's fixed time period and that time period has passed, no error message describing this condition is displayed when the alert is edited.
  • In the Dimensions and Reports widgets, saving a bookmark in widget view mode after clicking the Save Format button in widget edit mode fails with an SQL error.
  • Centering and resizing issues in the New KPI dialog and other dialogs launched from the KPI or KPI Manager widgets need to be addressed.
  • In the Diagrams widget, with Firefox as the browser, some text labels are misplaced.
  • Hijri dates are not correctly displayed in multiple widgets/elements.
  • In the Instances widget, the checkbox on each row is not properly aligned with the rest of the row.
  • In the Instances widget, refresh of the widget clears the checkboxes for all instances.
  • In the Instances widget, refresh of the widget causes any pop-up dialogs that are displayed to disappear.
  • Need to add "Show Instances" functionality to the Cognos Report Viewer widget.
  • With Internet Explorer as the browser, a Business Space page with a Cognos widget does not have a horizontal scrollbar.
  • In the Report Designer widget, the report picker dialog displays "Syntax error" upon loading.
  • When editing the Report Viewer widget, the Reset option is not enabled after making a change.
  • On WebSphere Portal, with Internet Explorer as the browser, the Instances widget does not load if Business Space is remote.

Other issues:
  • Code for migrating Alphablox widgets to Cognos refers directly to URLs instead of REST service endpoints.
  • REST services does not support WebSphere Lombardi Edition measure names.
  • REST interface documentation contains "WebSphere Business Monitor" instead of "IBM Business Monitor".

 

 

 

Original Publication Date

18 November 2011

[{"Product":{"code":"SS7NQD","label":"IBM Business Monitor"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.5.1.2;7.5.1.1;7.5.1;7.5.0.1;7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
20 July 2018

UID

swg27022112

Page Feedback