Universal Messaging 10.1 | Release Notes | What's New In Universal Messaging 10.0
What's New In Universal Messaging 10.0
Universal Messaging 10.0 is the successor of Universal Messaging 9.12.
Universal Messaging 10.0 includes new features, enhancements, and changes as described in the following topics.
Durable subscribers can be browsed in Command Central
Command Central can now be used to browse individual messages in durable subscribers in a Universal Messaging server instance, including messages waiting to be received by Integration Server triggers. You can view the size of individual messages and some properties of each message. You can also view the payload of string messages. All or individual messages can be deleted from the durable subscriber (for some durable subscriber types).
Enhanced Command Central support for Universal Messaging
Command Central can now be used to configure realm ACLs for Universal Messaging, allowing you to control which users can perform what actions at the realm level. You can also use Command Central to configure Java system properties for Universal Messaging. For Universal Messaging clusters, Command Central now displays whether each running instance is a master or slave in the cluster.
These capabilities can be accessed using the Command Central web user interface, command-line interface, REST API, and composite templates.
Utility for migrating webMethods Broker gateways configurations to Universal Messaging
For webMethods Broker users who have configured territories and gateways and have large numbers of document types (topics) configured in the gateway connections, migrating these to equivalent remote joins in Universal Messaging previously involved a lot of manual effort. Now, you can use a new utility that can read the gateway configuration from webMethods Broker and automatically establish the same remote joins in Universal Messaging.
Servers can be instructed not to restrict incoming messages from specific clients in low memory situations
A client session can request to bypass the existing server-side low-memory throttling. This is intended to allow administrators or administrative services to continue to be able to connect in order to resolve the low-memory situation.
JNDI assets can now be stored in existing (non-Universal Messaging) JNDI providers
Users who wish to use a JNDI provider for binding JNDI assets such as Connection Factories and Destinations can now store their Universal Messaging JNDI assets in a JNDI provider of their choice. This capability is only available through the respective API.
Cluster side-by-side upgrades to new machines are easier to manage
You can now use a migration utility to migrate cluster configurations to machines that are on different hosts from the original cluster.
Shared durables re-architected to improve efficiency and robustness
The implementation of shared durables has been re-written to improve efficiency. The new implementation performs tracking of durable objects in-place on the channel, rather than relying on additional internal stores. This approach saves memory and reduces the complexity of the solution, improving robustness. A new API has been developed to manage durable objects through the Universal Messaging native API. The Universal Messaging JMS library has also been updated to utilize the new durable implementation.
Configuration using Enterprise Manager is simplified
Enterprise Manager hides a number of configuration settings behind an Advanced button. These hidden settings are ones that are rarely recommended to be modified.
Additional tools are now available showing how to use the API with datagroups and illustrating how to publish and subscribe
Tools are provided that allow management of datagroups and illustrate how to use publish and subscribe.
Robustness improvements for installations using the default out-of-the-box configuration
The default configuration for new installations has been reviewed and tested to ensure Universal Messaging is robust.
Named object ID is a concatenation of client ID and durable subscriber ID
Named objects IDs are now a concatenation of the client ID and the durable subscriber ID. Previously Universal Messaging just used the durable subscriber ID provided by the client.
Removed and deprecated features in 10.0
The following Universal Messaging features are now deprecated or have been removed in Universal Messaging 10.0:
*The SharedDurableFilterBound option, found in the Durable Config group in the administrative API and Enterprise Manager/Command Central, has been migrated to be a System Property (-DQueuedSharedDurableFilterBound). This new system property is deprecated and will be removed in a future release.