===============================================================================
IBM® WebSphere® Business Integration (WBI) Monitor™ v4.2.4 Fix Pack2 - Readme File
===============================================================================

© Copyright International Business Machines Corporation 2002, 2004. All rights reserved. 

This file contains the new updates and fixed bugs in the IBM WBI Monitor v4.2.4 Fix Pack2. Please refer to the file named install_fix_pack2.html for the required information and steps required for installing IBM WBI Monitor v4.2.4 Fix Pack2.

New Updates

Event-Loss Prevention

WBI Monitor v4.2.4 Fix Pack2 provides the capability of preventing any loss of events due to any reason or error. The following features have been implemented to handle the reasons that caused loss of events.

Enhanced Exception Error Handling

The Exception Error Handling in WBI Monitor v4.2.4 Fix Pack2 has been enhanced and updated to eliminate any event loss due to database Dead Locks or Time Out exceptions. These exceptions are now handled by providing a proper rollback procedure that takes place prior to any event handling. This prevents any event deletion when these errors occur.

Using an Error Queue 

A new event queue named Error Queue  is now used to contain any events that cause errors while being processed. The types of errors include those that occur due to model mismatch between the implemented FDL file in MQ Workflow and the imported XML file, any runtime data entry errors, and any other unknown errors. The events processing in this Error Queue  is done as follows:

The event processor iteratively tries to process the events that are contained in the Error Queue  for a number of trials. Each event in this queue will be processed for maximum of 10 trials, after which it will not be processed if the error persists. In this case, the error is considered permanent and needs a user interaction to eliminate this error.

A section named Error Queue Details has been added to the Event Queue page in the WBI Monitor's Administration Utility. Clicking the Show Details button that exists in this section will open a new page named Event Recovery Page. This page contains the total number of events that exceeded their number of processing trials and still cause errors. The user has the option do one of the following actions on this page:

• Recover these events by resetting the processing trials counter for all these events and allowing for another 10 trials for each event. This is done by clicking the Recover button.
• Delete these events by clicking the Delete button. In this case, these events will be marked for deletion only and the Cleanup Manager will be responsible for deleting them in the idle time.
• Leave these events without processing or deletion and return to the Event Queue page by clicking the Back button.

Performance Enhancements

The WBI Monitor v4.2.4 Fix Pack2 provides the following performance enhancements:

1. Enhancing the DB2 concurrency during multithreaded event processing and multiple client access. New configuration parameters have been added to achieve this enhancement.
2. New Database Indices have been added to the Monitor schema to enhance the client response time of the Workflow Dashboard and Business Dashboard for basic and default views and reports.

Fixed Bugs:

1. APAR JR19471: Fixed the bug that occurred in Oracle database and caused the failure of importing XML files that contains more than 1000 parameters to the Monitor database due to the Oracle database limitation.
2. APAR JR19640: Fixed the bug that was locking out the default view in Workflow Dashboard if the user resized this view to smaller by rearranging the Business Measures when using Oracle database only.
3. APAR JR19780: Fixed the bug that occurred when the user created a Business Measure for the Predefined Metric CURRENT_ACTIVITY_NAME at Activity location Before Start, and the WBI Monitor Workflow Dashboard did not populate its value until the process instance is completed.

4. APAR JR19905 Fixed the bug that caused the WBI Monitor failure when starting any process instances in MQ Workflow after importing the FDL file in MQ Workflow and before creating the database triggers in the EventQueue database.

5. Improve the database access from Monitor Services to match the Minimum Wait and Maximum Wait System Properties.