TIBCO iProcess Insight(TM) 2.2.0 Hotfix 3 is now available for all supported platforms.
Welcome to "KB Articles"
TIBCO iProcess Insight(TM) 2.2.0 Hotfix 3 is now available for all supported platforms.
book
Article ID: KB0105122
calendar_today
Updated On: 01-13-2017
Products
Versions
TIBCO iProcess Insight
-
Not Applicable
-
Description
Description: September 14, 2009
TIBCO iProcess Insight(TM) 2.2.0 Hotfix 3 is now available for all supported platforms. Please see below for a list of issues that were addressed.
You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password to access the server at: ftp://support-ftp.tibco.com
Once you have successfully logged into the server, navigate to the "/available_downloads" directory. You will find the Hotfix packages located under:
Monitoring/iProcessInsight/2.2.0/hotfix-03
If you have any problems in finding or downloading this Hotfix, please let us know through an existing Support Request where this Hotfix was recommended, or by opening a new SR.
====================================================================== Issues addressed in 2.2.0_hotfix03 (This Release)
1-9YYCG0 Redeployment of the BF Aggregator was failing if changes were made to the project after initial deployment because the database schema for the project was not updated correctly. This issue has been fixed.
1-9Z6KXF When the alerts were set on a Date metric with 'Centered on Now' threshold condition, the alerts were not getting generated in a consistent manner. This issue has been fixed.
1-9Z6PCD The Step Monitor incorrectly set the value of the 'StartTime' metric to the 'case' start time instead of the 'step' start time in the database. This issue has been fixed.
====================================================================== Issues addressed in 2.2.0_hotfix02
1-9W9613 When TIBCO BusinessFactor Aggregator was deployed in Oracle database, cursor error leaks were observed occasionally. To fix this issue, set the value of the 'open_cursor' parameter to minimum 600 value in the init.ora file of Oracle.
1-9XCCT1 TIBCO BusinessFactor Aggregator did not process the messages in the order they were received. For example, Aggregator sent some messages even after the case was closed. This issue has been fixed.
1-9X18BT When EMS was configured as Server Input Transport for a BF Project and the 'Is Session Transacted?' option was enabled, EventFinder did not display any case data. This issue has been fixed.
====================================================================== Issues addressed in 2.2.0_hotfix01
1-9T5CGP Threshold conditions of type "Centered on Now" or "Period" were not correctly evaluated. As a result, alerts were not functional for date metrics with threshold conditions of type "Centered on Now" or "Period". This issue has been fixed.
1-9JXF8H The "bf:email" option was not seen in the Destination Type dropdown in the BAM Desktop > Profile > Delivery Options page.