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

New Updates:

1. Monitoring IBM WebSphere InterChange Server (WICS) Collaborations: WBI Monitor integrates now with the WebSphere InterChange Server (WICS) 4.2.2.2 Fixpack. This integration enables monitoring the WICS collaborations or collaboration groups. Refer to the WBI Monitor User Guide - Chapter 7: Monitoring WebSphere InterChange Server (WICS) Collaborations for details about this new update.
2. Support for Secured Socket Layer (SSL) Protocols: WBI Monitor can now be installed and deployed on a virtual host where a Secured
   Sockets Layer (SSL) is applied. In this case the “https” protocol should be used, instead of “http”, for typing the Monitor Web address.
3. Support for Clusters Deployment: WBI Monitor supports now clustering deployment using the WebSphere Deployment Manager, as one of the major features of the IBM WebSphere Application Server v5.x. Refer to the WBI Monitor Deployment Guide for details about this new update.
4. Support for Multiple Database TableSpaces Creation (Physical Database Design): WBI Monitor now allows controlling the distribution of the Monitor and the EventQueue Database tables and indices into a number of TableSpaces (up to 22 TableSpaces); 19 of which are created in the Monitor Database, and the remaining three are created in the EventQueue Database. The database tables and indices are grouped and categorized; such that each category can be assigned to a separate TableSpace. Refer to the WBI Monitor Deployment Guide for details about this new update.
5. Support for Multiple Event Processors (Multi Threading): WBI Monitor now allows initiating up to 20 event processors (as multiple threads) to process the incoming events; such that each processor is responsible for processing a number of events that is equal to the Event Count number. This leads to a significant increase in the event processing performance, especially for large generated events numbers. Refer to the WBI Monitor Administration Guide - System Properties Page section for details about this new update.
6. Reporting Against Ready State: WBI Monitor Business Dashboard reports can now display the process instances that a selected user is responsible for, when any of their activities happen to be ready in the queues.
7. The default state of all WBI Monitor Services is now "stopped". The user must start the required services after importing the organization xml files to start processing the events and to avoid loosing any data.

Fixed Bugs:

1. APAR JR18605: Fixed the bug in the System Properties Page of  the Monitor Admin Utility that caused using the user’s Credential as the user’s Password and vice versa, which in turns caused that the Process Instance Notifications was not worked properly.
2. APAR JR18666: Fixed the bug that takes place when a new user is added through the security page of the admin utility, and the group permissions of MQWF admin actions for this user are not inherited. The administrator now is allowed to set grant or deny permission for users added manually for admin actions permissions.
3. APAR JR18956: Fixed the Events Timestamp Duplication problem: In case of using Oracle database, the problem that existed due to the duplication of events time stamp has been solved to handle these events properly.
4. The DB2 Access in Monitor Event Queues has been enhanced.
5. The cleanup process for EventQueue redundant container data has been optimized.
6. Fixed the bug that caused a Business Measure value not to be updated, if the value was blank.
7. Fixed the bug that takes place when applying a filter while displaying a range of instances that is greater than 10 instances, and the filter query gives result of a number of instances less than 10.
8. Fixed the bug that caused exporting the Business Dashboard reports that contain a number of new items created one day earlier than the actual process instances date.
9. Fixed the problem that occurred when large data segments are used in Oracle database. This took place when the Process data associated with an event was larger than 1 K, and caused the ArrayOutofBound error.
10. When an activity instance is completed, the name of the user who completed the activity instance is now displayed in the Assigned Employee column of the Activity Instance table, instead of displaying a blank string.
11. Fixed the bug that caused displaying improper year in the Korean calendar.
12. Fixed the problem of using multiple event processors (Multi-Threading) when using DB2.