Universal Messaging enables both higher-release Java clients to connect to lower-release realm servers, and lower-release clients to connect to higher-release servers. The bi-directional client-server compatibility offers more flexible deployment strategies for both upgrades and daily operations, regardless of whether you are running higher-release clients, higher-release servers, or a mix. The functionality allows less release and upgrade planning between core components, resulting in faster deployments and less complexity in those deployments.

The Universal Messaging Java client version 10.5 and higher, and components built upon it including JMS and Resource Adapter, can connect to both lower-release and higher-release Universal Messaging servers. Java clients version 10.3 and lower can connect only to the same version or higher-release servers.

To use the bidirectional client-server functionality with Universal Messaging 10.3, 10.5, and 10.7, respectively, you must have the following Realm Server, Java Client, Shared Bundles, and Common Libraries fixes installed:

Be aware that not all fixes might be applicable to your installation. Software AG Update Manager displays only the fixes required by your installation.

The following table shows the backwards compatibility, that is, higher-release clients connecting to lower-release servers, between the different supported Universal Messaging client and server versions.

In addition, for information about how the bi-directional client and server compatibility impacts horizontal scalability environments, see Horizontal Scalability Behavior in a Mixed Landscape.