Product Documentation
Abstract
IBM Business Monitor development toolkit provides periodic fixes and updates for Version 8.0. The following is a complete listing of fixes for V8.0 with the most recent fix at the top.
Content
Version 8.0.1 Fix Pack 2
Version 8.0.1 Fix Pack 1
Version 8.0 Refresh Pack 1
Fix release date: 18 August 2014
Last modified: 18 August 2014
Status: Available (Recommended)
 | Download Version 8.0.1 Fix Pack 3 |
APAR | Description |
| When generating a monitor model based on a BPEL process, an inbound event is not created in the monitor model if the activity in the BPEL process marked for event monitoring is contained within an event or fault handler that is in turn within a scope block. | |
| Combining two monitor models generates an incorrect reference to an SVG diagram. |
Fix release date: 1 November 2013
Last modified: 1 November 2013
Status: Available (Recommended)
 | Download Version 8.0.1 Fix Pack 2 |
APAR | Description |
| When combining two monitor models with conflicting namespace prefixes in Integration Designer, an exception occurs and the monitor models are not combined. | |
| Content assist does not populate event parts that reference a type which is not directly referenced in the event model. |
Fix release date: 15 March 2013
Last modified: 15 March 2013
Status: Available (Recommended)
 | Download Version 8.0.1 Fix Pack 1 |
APAR | Description |
| When combining two monitor models in Integration Designer, if both monitor models use the same namespace prefix but with different namespace URIs, the namespace declarations are not properly merged. | |
| When generating a global monitoring context using the Global Monitoring Context wizard, an exception (CWMMV0627E) may occur. |
Fix release date: 16 November 2012
Last modified: 16 November 2012
Status: Available (Recommended)
 | Download Version 8.0 Refresh Pack 1 |
APAR | Description |
JR44235 | Export of the database schema creation scripts for a monitor model fails to correctly generate a CREATE TABLE statement for the Data Movement Service on DB2 for z/OS if the total width of the columns in the table is between 31,900 and and 32,768 bytes, resulting in failure of the script when it is executed (on DB2 for z/OS). |
[{"Product":{"code":"SS7NQD","label":"IBM Business Monitor"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.0.1.3;8.0.1.2;8.0.1.1;8.0.1;8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27036585