Usage Notes

Edit online

This section provides any additional information you need to work with the current release of this product.

  • Starting with version 11.1, the Universal Messaging client and server components support only Java 17. If an older Java release is required for the client, you should use an older version of Universal Messaging.

  • In version 11.1, the Universal Messaging Resource Adapter for application servers such as JBoss or IBM WebSphere Application Server has been removed. If you need to use the resource adapter, you should use an older version of Universal Messaging.

  • NUM-19405

    For any custom Java client application that uses the Universal Messaging administration or client API, you must add the following JDK option to the JVM that starts the application:

    --add-opens=java.base/java.lang=ALL-UNNAMED

  • After you create a server instance you cannot change the server instance name or the realm name. When you create the server instance, the server instance name is set to the realm name by default.

  • Universal Messaging client, non-admin sessions in an active/active cluster are always terminated if the server to which the client application connects is not in a good cluster state, that is, either master or slave state.

  • 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. For more information, see the section "Concepts \> Deployment \> Bi-directional Client and Server Compatibility" in the Universal Messaging documentation.

  • Behavior related to the pause-publishing functionality:

    • Modifying JNDI entries is not possible while publishing is paused. This is because JNDI entries are stored in a Universal Messaging channel.

    • If publishing is paused, editing a store in the Enterprise Manager will cause the events on the store to be lost, because they cannot be republished on the re-created store.

  • The server-side event filtering functionality in Universal Messaging does not support filtering of Google Protocol Buffer events using the “map” container type available in recent versions of the Google Protocol Buffer language.