Universal Messaging 10.1 | Release Notes | What's New In Universal Messaging 9.6
What's New In Universal Messaging 9.6
Universal Messaging 9.6 is the successor of Universal Messaging 9.5.
Universal Messaging 9.6 includes new features, enhancements, and changes as described in the following topics.
Improved JNDI Usability
When JNDI connection factories are managed using webMethods Universal Messaging Enterprise Manager, the JMS URL can now be specified during connection factory creation. In addition, the URL of existing connection factories can now be viewed or changed.
webMethods Suite Integration
Universal Messaging support in various webMethods products has been further extended. For details, see the webMethods Suite Release Notes for the various products.
Java Transport API
To provide a broker-less style of messaging, Universal Messaging now contains a new API, com.softwareag.um.io, which exposes the underlying communication drivers used within the Universal Messaging client and server, and enables direct synchronous and asynchronous communication between client applications using TCP/SSL sockets, SHM (shared memory), or RDMA protocols.
SASL Support
Universal Messaging now provides new security authentication features offering password authentication (Plain and Cram-MD5) via SASL. The Universal Messaging server now accepts username and password credentials from the client, and enables administrators to lock down servers in accordance with specific pluggable providers configured on the Universal Messaging server. These pluggable directory providers include User File (similar to .htaccess files) and LDAP.
MQTT Virtual Payload Types
Universal Messaging now provides MQTT users with the ability to define namespace roots where advanced namespace semantics can be applied. Specifically, the last part of the full topic namespace address can be used to publish / subscribe, indicating your preferred virtual payload type.
Added, Removed, Deprecated, or Changed APIs
The following new API is available:
Provides direct, broker-less synchronous and asynchronous communication between client applications, using Universal Messaging TCP/SSL sockets, SHM (shared memory), or RDMA protocols.