![[MQ 9.3.3 Jun 2023]](ng933.gif)
![[UNIX, Linux, Windows, IBM i]](ngmulti.gif)
What's new in IBM MQ 9.3.3 for Multiplatforms: base and Advanced entitlement
For Multiplatforms, IBM® MQ 9.3.3 delivers a number of new features and enhancements that are available with base product entitlement, and also with Advanced entitlement.
- Administration
- Application Development
-
- Performance improvements for processing of AMQP message acknowledgments
- Tracing enhancements for IBM MQ .NET and XMS .NET client libraries
- Error message improvements for IBM MQ .NET and XMS .NET clients SSL connectivity issues
- Remote messaging with the messaging REST API
- Containers non-install image added for Linux ARM64 / Apple Silicon
Additions to IBM MQ Console
Simplified administration through web console updates can provide easier navigation between the configuration and runtime relationships of IBM MQ resources. For example, administrators can view which applications are putting messages on queues and see the relationships between different queues. A new feature enables you to view the IBM MQ objects associated with a queue. For more information, see IBM MQ Console: Working with queues - CD only.
![[AIX, Linux, Windows]](ngalw.gif)
Performance improvements for processing of AMQP message acknowledgments
If an AMQP application is using QOS_AT_LEAST_ONCE(1) message delivery, the AMQP service waits for an acknowledgment from the application before it discards the copy of a message that it keeps after sending that message to the application.
Before IBM MQ 9.3.3, each message that has been acknowledged is removed from the queue individually. From IBM MQ 9.3.3 messages are removed in batches, which improves performance. For more information, see Removing acknowledged AMQP messages from the queue in batches.
dspmqver command now reports release type
The dspmqver command has been extended to include the release type, which makes it easy to see if the release is Continuous Delivery or Long Term Support.
The release type reported can be one of Long Term Support (LTS)
, Continuous Delivery(CD)
, or Long Term Support(LTS)and Continuous Delivery(CD)
. For more information, see dspmqver (display version information).
Tracing enhancements for IBM MQ .NET and XMS .NET client libraries
From IBM MQ 9.3.3, you can enable and disable tracing for the IBM MQ .NET and XMS .NET client libraries without needing to restart the application.
You can use the mqclient.ini file to enable traces for the IBM MQ .NET and XMS .NET client libraries (.NET Standard, .NET Framework, and .NET 6). You can also enable and disable tracing dynamically. When the application is running, if the mqclient.ini file is modified, created, or deleted, the IBM MQ .NET and XMS .NET client reads the properties of the trace section again and then enables or disables the trace, so that restart of the application is not needed.
For more information, see Trace stanza of the client configuration file, Tracing IBM MQ .NET applications with mqclient.ini, and Tracing XMS .NET applications with mqclient.ini.
Error message improvements for IBM MQ .NET and XMS .NET clients SSL connectivity issues
From IBM MQ 9.3.3, the IBM MQ .NET client and XMS .NET client provide improved and more meaningful information about SSL enabled connection failures, helping you understand an issue and resolve this type of issue more quickly.
Improvements made to the IBM MQ .NET and XMS .NET client libraries (amqmdnetstd.dll) and (amqmxmsstd.dll) provide a more specific exception mechanism for SSL-related issues. The MQRC reason codes are in line with the other .NET client libraries, such as C. For more information, see Common SSL error codes thrown by IBM MQ .NET client libraries and Common SSL error codes thrown by XMS .NET client libraries.
Remote messaging with the messaging REST API
From IBM MQ 9.3.3, you can use the messaging REST API to connect to remote queue managers for messaging. Remote queue managers can be queue managers within another installation, or on another system. Therefore, you can now use a single installation to run the mqweb server and connect to any queue manager with the messaging REST API.
For more information about remote messaging with the messaging REST API, see Setting up a remote queue manager to use with the messaging REST API.
Containers non-install image added for Linux ARM64 / Apple Silicon
If you have strong container development skills, you can use the make files supplied in the
mq-container
GitHub repository to build your own production container image. This
image works in conjunction with a set of non-install (unzippable) IBM MQ images that help you build a container image that can run
under the OpenShift®
anyuid
Security Context Constraint. From IBM MQ 9.3.3, the set of non-install images includes an image that
works with the Linux® ARM64 and Apple Silicon platforms.
For more information, see Building a sample base IBM MQ queue manager image.