What's New in Universal Messaging 10.4

Universal Messaging 10.7 | Release Notes | What's New in Universal Messaging 10.4

Universal Messaging 10.4 is the successor of Universal Messaging 10.3.

Universal Messaging 10.4 includes new features, enhancements, and changes as described in the following topics.

New features in v10.4

The following Universal Messaging features have been added in Universal Messaging 10.4:

Support for channel and queue snoop in Command Central

You can snoop on events on a Universal Messaging channel or queue as well as purge events from a channel or queue, using the Command Central web user interface and command-line interface.

For information, see the sections Snooping on Channels, Snooping on Queues, Channel Snoop, and Queue Snoop in the Administration Guide.

Support for publishing events on channels and queues in Command Central

You can publish events, including Protobuf events, on a Universal Messaging channel or queue, using the Command Central web user interface and command-line interface.

For information, see the sections Publishing Events and Event Publishing in the Administration Guide.

Support for .NET Standard 2.0

The APIs Nirvana DotNet.dll, Nirvana nAdminAPI.dll and Nirvana.Reactive.dll have been tested to be compatible with .NET Standard 2.0. For the verification, the ".NET Portability Analyzer" tool from Microsoft is used.

For information see the section Using UM API libraries for .NET in .NET Standard projects in the Developer Guide.

Support for deleting clusters using the Tools Runner application

The Tools Runner application (runUMTool) has been extended with a new command DeleteCluster. This command allows you to delete an existing cluster.

For information, see the topic Syntax: Cluster Tools in the section Command Line Administration Tools of the Administration Guide.

Changed features in v10.4

The following Universal Messaging features already available in the previous product release have been changed in Universal Messaging 10.4:

Multiplex session authentication

There is a change in the way user names are handled for client authentication in a multiplex session.

For details, refer to the topic Multiplex session authentication in the section Multiplexing Sessions in the Concepts guide.

Horizontal Scalability

Universal Messaging sessions using the "horizontal scalability" feature now support automatic (re-)connection to realm servers in the scalability set that are offline/unavailable when the session is created or initialized.

Also, HS sessions support connecting to various connection interfaces, e.g. NHP/NHPS/NSP/NSPS, and you can use a combination of these in a single HS RNAME.

For details, refer to the topic Usage Notes for Horizontal Scalability in the section Horizontal Scalability in the Concepts guide.

Updated System.Reactive Libraries for .Net Reactive samples

The .Net Reactive Extensions (Rx) sample programs have been updated to use System.Reactive libraries v3.1.1. In the previous product release, version 1.0 of these libraries was used.

The sample programs are located under in folder <InstallDir>\UniversalMessaging\docnet\examples.

Using AMQP in clustered environments

Universal Messaging now supports AMQP 1.0 in clustered environments.

At the moment, automatic failover of AMQP clients is not supported. If the AMQP connection fails it is the responsibility of the AMQP client application to reconnect to another node in the cluster.

Note:
For the initial release of V10.4, the new functionality is provided as a software fix that you need to install after the standard product installation procedure has completed. To install the fix, you can use either Command Central or the Software AG Update Manager. If you wish to use the Update Manager, general instructions are provided in the document Using Software AG Update Manager that you can find on the Software AG documentation web site.

Deprecated features in v10.4

The following Universal Messaging features are now deprecated in Universal Messaging 10.4. Features listed as deprecated are still available in the product, but will be removed in a future release.

The store type "transient"

The channel/queue type "transient" is deprecated in v10.4 and will be removed in a future version of the product.

Realm configuration properties

The following realm configuration property is deprecated:

SyncPingSize

The realm configuration properties are described in the section Realm Configuration in the Administration Guide.

Removed Features in v10.4

If features have been removed in Universal Messaging 10.4, they are listed in this section.

There are currently no removed features in v10.4.

Documentation Changes

Operations Guide

The product documentation set has been extended to include a new Operations Guide. This guide gives guidance on how to perform day-to-day operation and maintenance tasks, and includes suggestions on how to deal with standard questions in the areas of troubleshooting and maintenance.

For details, refer to the section Operations Guide.

Dead Event Store

The description of how the dead event store is used for channel processing has been updated.

For details, refer to the topic Dead Event Store restrictions for durable subscriptions in the section Channel Attributes in the Concepts guide.

Java Service Wrapper

Several components of Universal Messaging make use of the Java Service Wrapper, which is an application provided by developed by Tanuki Software, Ltd. Information about the Universal Messaging components that use the Java Service Wrapper, and how to configure it, have been added to the documentation.

For details, refer to the section Configuring the Java Service Wrapper in the Administration guide.

Startup and Shutdown Procedures

Documentation has been added to better describe the procedures involved in starting up and shutting down a Universal Messaging Server.

For details, see the sections Starting the Realm Server and Stopping the Realm Server in the Installation Guide.

Additional descriptions for Clustering

Some topics such as the following have been added in the Clustering section of the Administration Guide.

Roles and Responsibilities for Configuring an Active/Passive Cluster

Configuring a Universal Messaging Active/Passive Cluster on UNIX

Cluster Verification

Failover Mechanism in an Active/Passive Cluster

Virtual IP Address of an Active/Passive Cluster

Restrictions for Shared Memory connections

A note has been added to the documentation that Shared Memory (SHM) connections are not supported on Solaris with SPARC architecture.

See the related note in the section Shared Memory (SHM) in the Concepts guide.

Rules for naming channels and queues

A section has been added to the documentation to describe the valid set of characters that can be used when naming a new channel or queue.

For details, see the topic Valid Channel and Queue Names on the page Creating Channels in the Enterprise Manager section of the Administration Guide.

Removal of some client JAR files

In previous product versions, some client Jar files were removed by design from the product delivery, but this was not stated clearly. The following table indicates Jar files that were delivered with previous product versions, but which are not delivered as Jar files any more. Their classes have now either been folded into other Jar files, or have been removed from the product altogether.

Previously available JAR File	Description	Status
nJ2EE.jar	Provided Universal Messaging support for interacting with Application servers that support J2EE.	The Jar file is no longer available. The Universal Messaging product now contains a resource adapter for use with application servers. See the topic Resource Adapter for JMS in the Java section of the Developer Guide for related information.
nAdminXMLAPI.jar	Provided Universal Messaging Configuration XML Import / Export functionality.	The Jar file is no longer available, but the contents have been folded into nAdminAPI.jar.
nP2P.jar	Provided Universal Messaging Peer-to-Peer functionality.	The P2P functionality was removed from the product in version 9.12. The Jar file is no longer available, and the contents have not been folded into any other Jar file.

For the list of currently delivered client JAR files, refer to the section Client Jars in the Concepts guide.