Product Documentation
Abstract
IBM WebSphere Business Monitor development toolkit provides periodic fixes and updates for Version 7.0. The following is a complete listing of fixes for V7.0 with the most recent fix at the top.
Content
Version 7.0 Fix Pack 5
Fix release date: 26 June 2012Last modified: 26 June 2012
Status: Available (Recommended)
APAR | Description |
When importing an event into the Integrated Test Client in the Monitor model editor and emitting to a monitor model, e.g. for use in debugging, the CBE headers are generated anew, and a default empty namespace is removed. | |
When generating JEE projects for a monitor model that has a large number of XPath expressions, project generation may fail due to the error "The code for the static initializer is exceeding the 65535 bytes limit". |
Version 7.0 Fix Pack 4
Fix release date: 3 June 2011Last modified: 3 June 2011
Status: Available (Recommended)
APAR | Description |
In the monitor model editor, the string entered for Text Value in the Visual Model tab is truncated to 256 characters. | |
In the Monitor Model Editor, if the length of the ID for a metric or key metric is 1, J2EE project generation will fail with a java.lang.StringIndexOutOfBoundsException. | |
In the Monitor Model Editor, when choosing to "Update from Application - <app_name>", a new event in an event group will be set to create a new instance, even though it should just deliver to an existing instance. | |
The following internally identified issues have been resolved:
|
Version 7.0 Fix Pack 3
Fix release date: 3 September 2010Last modified: 3 September 2010
Status: Available (Recommended)
APAR | Description |
When generating a monitor model from a BPEL process, if you select the last node in an inline human task chain without selecting the task's parent task node, generation of the monitor model will fail. | |
If a monitor model meets certain conditions, processing of recurring wait time triggers will result in StaleConnectionExceptions. | |
The Average aggregate function includes null values in the instance data as zero values. | |
With DB2 z/OS as the database, calculation of a KPI based on a stopwatch may fail due to an SQL overflow error. | |
Need to create indexes based on the UPPER column function to improve dashboard retrieval performance for modeled KPIs based on a case insensitive string metric data filter. | |
On Oracle, every cross-version monitoring context view is based on "UNION" instead of "UNION ALL", resulting in slower cross-version data retrieval in the dashboards. | |
After migration of data for a monitor model installed on WebSphere Business Monitor Version 6.1.2 to Version 7.0, the model data cannot be viewed in Business Space, and new inbound events will not be processed due to correlation errors. | |
For a monitor model using 6.1 multi-threaded processing and event reordering, if an incoming event does not contain sequence or instance hierarchy information, it will cause event consumption to stop. | |
The following internally identified issues have been resolved:
|
Version 7.0 Fix Pack 2
Fix release date: 30 April 2010Last modified: 30 April 2010
Status: Available (Recommended)
APAR | Description |
The monitor model editor cannot generate the correct type for an event part when the associated business object is defined as an enumeration. | |
In WebSphere Integration Developer, refactoring a process module for which a WebSphere Business Monitor monitor model has previously been generated may fail with a NullPointerException. An error dialog is displayed that contains the following text: An exception has been caught while processing the refactoring 'FileLevel Refactoring Processor'. | |
You cannot set the start or end value of a range for a duration KPI to be more than 99 days. | |
If a generated monitor model contains a user defined function (UDF) that is used in XPath expressions in the model, and the UDF includes external libraries, when you attempt to search for instances or drill down on an instance (to view child monitoring context instances) in the Instances widget in the dashboard, the operation fails and an error message is displayed by the widget. | |
If a WSDL file in a monitor model project, or a project referenced by a monitor model project, contains an incorrect import statement (for example, the path specified in the "location" attribute is incorrect), J2EE project generation forthe monitor model fails. | |
The following internally identified issues have been resolved: Issues in monitor model generation:
Issues in the Monitor Model Editor:
Issues in generated monitor models:
| |
In WebSphere Integration Developer, refactoring a process module may incorrectly modify schema import statements in the associated monitor model projects, resulting in monitor model validation errors in the monitor model editor that prevent J2EE projects from being generated. |
[{"Product":{"code":"SSSRR3","label":"WebSphere Business Monitor"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0.0.5;7.0.0.4;7.0.0.3;7.0.0.2;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27019409