IBM Support

WebSphere Business Monitor development toolkit V7.0 Fix Pack 2 (7.0.0.2)

Download


Abstract

This document describes the features and fixes in Fix Pack 2 for WebSphere Business Monitor development toolkit Version 7.0. (Note: This is the first Fix Pack for Version 7.0.)

Download Description

The table below shows the new features in WebSphere Business Monitor development toolkit V7.0.0.2.

FeatureDescription
Updated Information CenterThe IBM WebSphere Business Monitor 7.0 Information Center has been updated for V7.0.0.2.

If you have a locally installed version of the documentation, see Updating the local information center.
Windows 7 supportWebSphere Business Monitor development toolkit V7.0.0.2 adds support for the Windows 7 operating system.
Hijri calendar supportThe calendar widget that is displayed to assist with entry of values for Date, Time, and DateTime elements in monitor models now supports the Hijri (Islamic) calendar, both civil and religious, in addition to the Gregorian calendar.


The table below shows all of the issues resolved in WebSphere Business Monitor development toolkit V7.0.0.2.

APARProblem Description
JR34877The monitor model editor cannot generate the correct type for an event part when the associated business object is defined as an enumeration.
JR35027In 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'.
JR35100You cannot set the start or end value of a range for a duration KPI to be more than 99 days.
JR35340If 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.
JR35437If 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 for the monitor model fails.
JR36121The following internally identified issues have been resolved:

Issues in monitor model generation:
  • When a monitor model is generated from a process (in WebSphere Integration Developer), NullPointerException messages are written to the log when the name of an event selected for the model contains spaces.

Issues in the Monitor Model Editor:
  • Comparison of two monitor models might not flag all differences between the models.
  • The calendar widget for editing a Date, Time, or DateTime metric always defaults to GMT instead of the system time zone.
  • When the time zone of a DateTime value is GMT, the time zone information is not included in the value.
  • When you edit the start or end date of a KPI time filter based on a metric of type Date, a time value is displayed in the calendar widget even though it has no meaning.
  • The Problems view displays a warning message when a rolling or repeating time filter is selected for a KPI with frequency yearly, monthly, or quarterly.
  • If a single quote character or ampersand character is included in a monitor model name, J2EE project generation fails. (In Fix Pack 2, J2EE project generation will be blocked with a notification to remove these characters from the model name.)
  • Validation warnings are required when the recurring wait time for a time based trigger is set to 1 minute because of possible performance impact.
  • In the visual model, if a metric is referenced in a condition expression and the test button is pressed without that metric being given a test value, the error "UNRECOVERABLE: XPath.ReferenceNotFound (x - y)" is displayed.
  • The monitor model debugger encounters a fatal error when evaluating an expression that compares a DateTime value without time zone information with a DateTime value with time zone information.

Issues in generated monitor models:
  • If a model contains a standard deviation calculation in an expression, rounding errors may occur, which can result in event processing failures.
  • If the same trigger updates a counter in a monitoring context and another counter in a child monitoring context, one or both counters are not consistently updated when the trigger fires.
  • With WebSphere Application Server Feature Pack for XML V1.0.0.5, the wbm:send-events() function may fail, causing event processing failures (failing events will be sent to the failed event queue).
  • In a generated monitor model schema for DB2 z/OS, a stored procedure for Data Movement Service might exceed the limit of 70 characters, resulting in failure to install the stored procedure to the database during schema creation.
  • With DB2 z/OS as the database, the value of a stopwatch may fail due to an SQL overflow error. The following error is written to SystemOut.log:

    KpiCalculator E com.ibm.wbimonitor. kpi.KpiCalculator executeSQLStatement() DB2 SQL Error: SQLCODE=-802,SQLSTATE=22003, SQLERRMC=FIXED POINT OVERFLOW;MULTIPLICATION;INTEGER;
  • General comparisons in expressions (comparisons using =, !=, <, <=, >, or >=) are not evaluated correctly if one or both operands are empty.
JR36129In 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.

Prerequisites

  • Please ensure that your WebSphere Business Monitor development toolkit environment meets the system requirements documented at: http://www.ibm.com/support/docview.wss?uid=swg27018594
  • To apply this Fix Pack, you must be at WebSphere Business Monitor development toolkit Version 7.0.0.0, installed under Rational Application Developer.
  • Rational Application Developer must be upgraded to Version 7.5.5.1.
  • If the development toolkit was installed under WebSphere Integration Developer, you must install WebSphere Integration Developer V7.0 Fix Pack 2 (with the Monitor Model editor feature selected) to update the development toolkit to V7.0.0.2.

[{"INLabel":"Installing WebSphere Business Monitor Toolkit V7.0.0.2","INLang":"English","INSize":"2222","INURL":"http://www.ibm.com/support/docview.wss?rs=802&uid=swg27018390"}]
On
[{"DNLabel":"Monitor Toolkit V7.0 Fix Pack 2","DNDate":"4/30/2010","DNLang":"English","DNSize":"57815902","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"http://www.ibm.com/support/fixcentral/quickorder?fixids=7.0.0-WS-WBM-FP0000002_TK&product=ibm%2FWebSphere%2FWebSphere%20Business%20Monitor&source=dbluesearch","DNURL_FTP":" ","DDURL":null}]
[{"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.2;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Problems (APARS) fixed
JR34877 JR35027 JR35100 JR35340 JR35437 JR36121 JR36129

Document Information

Modified date:
15 June 2018

UID

swg24026265

Page Feedback