===============================================================================
IBM® WebSphere® Business Integration (WBI) Monitor™ v4.2.3 Fix Pack 2b7 -
Readme File
===============================================================================
Welcome to the IBM WBI MonitorTM 4.2.3 - Fix Pack 2b7 Readme file. Please read this document before installing WBI Monitor 4.2.3 - Fix Pack 2b7. For information about installing this fix pack, please refer to the file named install_fix_pack2.html that is shipped with this fix pack.
This file includes the following contents:
2 New Updates and Changes in this Fix Pack
2.1.1 Export Process Instance Values as CSV
2.1.2 Command Line Import Utility
#################################################################################
THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION
The license agreement for this product refers you to this file for details
concerning terms and conditions applicable to third party software code included
in this product, and for certain notices and other information IBM must provide
to you under its license to certain software code. The relevant terms and
conditions, notices and other information are provided or referenced below.
Please note that any non-English version of the licenses below is unofficial and
is provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file, is the
official version.
===========================================
JDOM CODE: The Program includes software developed by the JDOM Project (http://www.jdom.org/).
IBM obtained the JDOM software under the terms and conditions of the following
license from the JDOM project:
/*--
Copyright (C) 2000 Brett McLaughlin & Jason Hunter.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions, and the disclaimer that follows
these conditions in the documentation and/or other materials
provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products
derived from this software without prior written permission. For
written permission, please contact license@jdom.org.
4. Products derived from this software may not be called "JDOM", nor
may "JDOM" appear in their name, without prior written permission
from the JDOM Project Management (pm@jdom.org).
In addition, we request (but do not require) that you include in the
end-user documentation provided with the redistribution and/or in the
software itself an acknowledgement equivalent to the following:
"This product includes software developed by the
JDOM Project (http://www.jdom.org/)."
Alternatively, the acknowledgment may be graphical using the logos
available at http://www.jdom.org/images/logos.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
This software consists of voluntary contributions made by many
individuals on behalf of the JDOM Project and was originally
created by Brett McLaughlin <brett@jdom.org> and
Jason Hunter <jhunter@jdom.org>. For more information on the
JDOM Project, please see <http://www.jdom.org/>.
*/
===========================================
SITRAKA INC. COMPONENTS: The Program contains material that is © 1997-2002 by
SITRAKA, all rights reserved. The Sitraka software may contain materials owned
by Sun Microsystems, Inc. If so, all title in and copyright to the Java™
Technology are owned or licensed by Sun Microsystems, Inc., all rights reserved.
#################################################################################
2 New Updates and Changes in this Fix Pack
2.1.1 Updated EventQueue Page
The Event Queue Page in the WBI Monitor Administration Utility has been updated to exclude the Events Table and display a hyperlink named Show Events Summary. Clicking this hyperlink displays a new page that contains the total number of events that have not been processed yet by the event processor.
2.1.2 Reporting Against Ready State
WBI Monitor now can display the users which have an activity ready in their queues in the Business Dashboard reports as follows:
Important Note: For the Char type Business Measures that hold string values, the calculated value must not exceed 63 characters. Otherwise the value will be truncated.
Allow copying and pasting text in the Constraint Builder dialog box of the Security Page in the WBI Monitor Administration Utility.
The Weighing Factor field that appears when the user selects the Trend Analysis in the Business Dashboard's Configuration page accepts now values between 0 to 1
Improved access to MQ Workflow Tables: All WBI Monitor queries against the events tables have been tuned to avoid full table scans. Necessary indexes have been added to enhance the response time, and keep working even if it is shut down till a build up of millions of events was accumulated.
Tuned Notification Processing: Notification processing is tuned to avoid running the previously reported SQL statements that scan all the users many times within a transaction.
PMR 84456,180,000, The DB2 Access in Monitor Event Queues has been enhanced.
JR18456 - In any saved views of the Workflow Dashboard, it is applicable now to navigate through different pages if the Process Instances table includes more than 10 instances.
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.
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.
The events for the "FMCINTERNALNOOP" activity (NOOP Activity) is now ignored and no related errors appear in the log file.
JR 18956 - Fixed the Events Timestamp Duplication problem: In case of using Oracle database, the problem that was exist due to the duplication of events timestamp has been solved to handle these events properly.
PMR 17808,379,000: In the Event Queue Page of the WBI Monitor Administration Utility, a blank value is now displayed for the "Last Processed Event" if there is no events in queue, instead of displaying the GMT value of 01/01/1970.