Release Notes
|
The most-significant update to UM version 6.5 is the introduction of the Ultra Messaging System Monitoring option.
The following new features and enhancements apply to UMS, UMP, and UMQ products.
Change Request | Description |
---|---|
7911 | You can now configure Ultra Messaging to use Solarflare Onload to select transport sockets for acceleration. Onload is a kernel-bypass technology that accelerates message traffic and operates with Solarflare 10GbE Ethernet NICs. See Solarflare® Onload for more information. |
7974 | The lbmrd daemon now includes command line option '-f ' or '--lic-file ' to let you specify the Ultra Messaging license file. |
The following new features and enhancements apply to UMP and UMQ products.
Change Request | Description |
---|---|
7478 | The Persistent Store Web Monitor now displays the Session ID on the Store page, Source page, and Receiver page. |
The following new features and enhancements apply to the UMQ product.
The following new features and enhancements apply to the Dynamic Routing Option (DRO).
Change Request | Description |
---|---|
7694 | You can now use the LBT-SMX transport to send ingress message traffic to a UM Router (DRO). The UM Router no longer ignores topic resolution traffic from a LBT-SMX source. You still cannot, however, use LBT-SMX to send egress traffic from a UM Router. |
In conjunction with the Ultra Messaging 6.5 release, Informatica has introduced the Ultra Messaging System Monitor Option (UMSM). Administrators can use UMSM to monitor components of an Ultra Messaging deployment. The UMSM dashboard displays the status of components, such as UM hosts, transports, topic resolution domains, and application instances, as well as UM statistics.
UMSM monitors the messaging traffic of Ultra Messaging versions 5.0 and later.
With the Ultra Messaging 6.5 release, Ultra Messaging Automatic Monitoring sends the following aggregated receiver statistics and subscription information to UMSM:
As the collection of aggregated statistics can increase the latency of message delivery, Ultra Messaging does not collect them by default. You can enable UMSM to collect the aggregated message loss statistics with the UM configuration options, monitor_interval (receiver) and monitor_interval (wildcard_receiver). You can access the aggregated receiver statistics with UMSM. The lbmmon API does not provide access to the aggregated receiver statistics.
The Ultra Messaging 6.5 release contains a third new UM configuration option, receiver_callback_service_time_enabled (context), which enables UMSM to maintain receiver callback service times. The lbmmon API does not provide access to the receiver callback service times.
The following bug fixes apply to UMS, UMP, and UMQ products.
The following bug fixes apply to UMP and UMQ products.
The following bug fixes apply to the UMQ product.
The following bug fixes apply to the Dynamic Routing Option (DRO).