You can use Software AG Installer to create Docker images for a Universal Messaging server on Linux operating systems. The Installer client creates a Docker image with a Universal Messaging server entry point and support for command-line tools similar to the images provided in the Software AG repository on Docker Hub. For a detailed description of this feature with usage examples, see the documentation about creating Docker images with Software AG Installer on Linux in the Using Software AG Installer guide.

You can export Protobuf definitions from a Universal Messaging store in the following ways:

For more information about configuring SSL/TLS in Universal Messaging, see Server SSL Configuration.

You can configure Universal Messaging to use custom HTTP headers from the client HTTP connection request for JAAS authentication. To enable JAAS authentication using HTTP headers, you configure a new system property, com.softwareag.um.server.authentication.http.extraHeaders.

For more information about JAAS authentication with HTTP headers, see Configuring JAAS Authentication with HTTP Headers.

You can use JAAS authentication with HTTP headers to authenticate clients that did not provide a password. To enable authentication without a password, you configure a new system property, com.softwareag.um.server.authentication.simpleAuthenticationEnabled.

For more information about authenticating clients that did not provide a password, see Enabling Authentication Without a Password.

Universal Messaging is backwards and forwards compatible with the Universal Messaging Java client, JMS, and Resource Adapter. In addition to clients connecting to the same or higher-release servers, Universal Messaging enables Java clients version 10.5 and higher to connect to lower-release servers. The feature was introduced in Universal Messaging 10.7.

For more information about the functionality and compatible client and server versions, see Bi-directional Client and Server Compatibility.

You can use the following objects and APIs on the Java client, which were added in version 10.7, to identify the release version of the components that are in use in your landscape:

For more details, see the Universal Messaging Java Client API documentation.

Now that Universal Messaging is backwards and forwards compatible with Java clients, for consistency in a mixed server environment, you must restrict the HS URL of your application to use the lowest server release version available in the HS landscape. For the purpose, you can use a new parameter, hsReleaseVersion, as part of the HS URL. This functionality has been delivered with Universal Messaging 10.7 Fix 1.

For more information about the functionality and about configuring the hsReleaseVersion parameter, see Horizontal Scalability Behavior in a Mixed Landscape.

You can use the ServerReleaseVersion tool to obtain the release versions for a list of Universal Messaging servers or for servers that are part of a Horizontal Scalability (HS) URL. For HS servers, the tool generates an HS URL that contains the hsReleaseVersion parameter.

For more information about using the tool, see The ServerReleaseVersion Tool.

Universal Messaging can use the NHP and NHPS interfaces to communicate with MQTT and AMQP protocol clients. This makes configuring Universal Messaging easier because the NHP and NHPS interfaces can support all protocols of the server on a single interface.

You can now use the new LogLevelOverride realm configuration property to configure the server log level when the server uses the Log4j2 logging framework. This parameter is only supported when the server is running as a Docker container.

If you set LogLevelOverride to true, you can configure the fLoggerLevel property. A false value for LogLevelOverride restores the configuration from log4j2.xml and overrides fLoggerLevel in the Enterprise Manager.

For more information about the logging configuration, see Realm Configuration.

The new functionality is provided with the Universal Messaging 10.11 Fix 8.

A new client property that specifies the number of missed server-side keep-alive intervals before the client closes a connection. The property is introduced in Universal Messaging 10.11 Client Fix 12.

For more information about the property, see Client Parameters.

A new realm configuration property that defines the number of concurrent connections to a Universal Messaging server per user. The property is introduced in Universal Messaging 10.11 Fix 13. For more information about using the property, see Realm Configuration.

The new JoinLastEIDMismatchCheck checks for joins that are ahead of the channel's last EID. The check is introduced in Universal Messaging 10.11 Fix 14. For more information, see Running a Configuration Health Check.

A new system property that enables the server to report warning messages if a connection takes more than a specified time to authenticate. The property is introduced in Universal Messaging 10.11 Fix 6. For more information about using the property, see Server Behavior when Authenticating Connections.