Released: April 2023
This release was updated to ensure compatibility with the TIBCO EBX® Add-ons Bundle version 4.5.17.
This release contains no changes in functionality.
This release contains no changes to third-party libraries.
This release contains no closed issues.
This release contains no known issues.
Release Date: September 18, 2020
This release contains the following updates:
The add-on has been updated to support the OpenJDK8 and OpenJDK11 libraries.
Libraries were updated to fix some potential issues.
Release Date: June 23, 2020
[MTRN-148] The documentation was updated.
Release Date: November 8, 2019
The method used to delete records in the Event monitoring table has been updated.
Release Date: June 20, 2019
The add-on has been updated to ensure compatibility with the TIBCO EBX® 5.9.4 release.
Release Date: October 26, 2018
The EBX® Activity Monitoring Add-on has undergone significant updates to ensure compatibility with the EBX® 5.9.0 GA release.
Release Date: September 6, 2017
[27647] An unexpected exception occurs when the user fails to log-into the Web Service.
Release Date: March 17, 2017
[24404] It is now possible to track failed logins via EBX® Activity Monitoring Add-on.
Release Date: May 19, 2016
User log in and log off activity can be monitored via the EBX® event broker and stored by the EBX® Activity Monitoring Add-on.
An additional color is available to differentiate between an operation that is stopped normally and one that is stopped because of exceeding its maximum duration.
[15807] The same color can be assigned to more than one status.
Release Date: February 26, 2016
[19415] The user guide title and table of contents is not up-to-date.
Release Date: November 10, 2014
It is now possible to archive the monitoring log and to restore it in a dedicated data space. The archive process can be launched automatically when a maximum size of the log data is reached, or through the EBX® scheduler.
Release Date: June 19, 2014
It is now possible to add any bespoke status to monitor operation execution. Every status can be configured with a specific color to differentiate it in the report UI.
The ready-to-use status 'Wait to be killed' has been added and allows you to request the termination of an operation.
A service is now available to purge the monitoring log.
Release Date: April 8, 2014
A directory is used to register the operations that can be monitored.
The 'Activity monitoring' table records all data related to the execution of the monitored operations.
Color coding is configured to make the operations for which the expected execution time has been exceeded stand out from other operations.
An API is provided to handle the communication protocol between the operation and the monitor.