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 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
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. |
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. |
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". |
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. |
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:
Operational issues:
Issues in Cognos functionality:
Issues in fine grain security:
Issues in the administrative console:
Issues in the IBM Business Monitor widgets:
Other issues:
|
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:
Operational issues:
Issues in Cognos:
Issues in profile management:
Issues in the administrative console:
Issues in the WebSphere Business Monitor widgets:
Other issues:
|
Original Publication Date
18 November 2011
Was this topic helpful?
Document Information
Modified date:
20 July 2018
UID
swg27022112