New IBM MQ 9.1.2 features for Multiplatforms

Uniform clusters

IBM MQ 9.1.2 introduces uniform clusters, which are a specific pattern of an IBM MQ cluster that provides applications with a highly available and horizontally scaled collection of queue managers. When an application interacts with a uniform cluster as a single group, the queue managers work together to maintain an even balance of application instances across the cluster, even across queue manager maintenance and restarts.

For more information, see Uniform clusters.

JSON format client channel definition table

IBM MQ 9.1.2 introduces a JSON format for the client channel definition table (CCDT). This gives various improvements over the existing binary format CCDT, including the ability to define duplicate channel definitions of the same name.

This is a client-side feature (that is, you need an IBM MQ 9.1.2 client, not an IBM MQ 9.1.2 queue manager).

For more information, see Configuring a JSON format CCDT.

Custom application identification

In addition to the existing ability to choose an application name on Java or JMS client applications, IBM MQ 9.1.2 extends this to other programming languages.

See Specifying the application name in supported programming languages for more information.

Enhanced REST messaging performance with connection pools

To optimize the performance of the messaging REST API, connections to IBM MQ queue managers are pooled. That is, instead of each REST request creating, using, and destroying its own connection, each REST request uses a connection from a connection pool.

By default, 20 connections are available for each queue manager pool. You can change the maximum number of pooled connections and the default behavior of the messaging REST API when all connections are in use by using the setmqweb properties command. For more information, see Configuring the messaging REST API.

Support for Microsoft .NET Core on Linux

IBM MQ 9.1.1 added support for .NET Core for applications in Windows environments.

From IBM MQ 9.1.2, IBM MQ supports .NET Core on IBM MQ .NET and XMS.NET on Linux platforms in addition to Windows platforms.

For more information, see Installing IBM MQ classes for .NET Standard and Installing IBM MQ classes for XMS .NET Standard.

Enhancements to the IBM MQ Bridge to Salesforce

IBM MQ 9.1.2 introduces additional configuration options that permit two major classes of additional topology, and changes to the way in which tracing and logging work.

For more information, see Additional configuration options for IBM MQ Bridge to Salesforce and runmqsfb for details of the changes to this command.

Full WebSphere Liberty XA support with client channel definition tables

When using WebSphere® Liberty 18.0.0.2 onwards, with IBM MQ 9.1.2, you can make use of queue manager groups within the client channel definition table (CCDT) in conjunction with XA transactions. This means that it is now possible to make use of workload distribution and availability, provided by queue manager groups, whilst maintaining transaction integrity. For more information, see Full Liberty XA support with client channel definition tables.

This is a client-side feature, that is, you need an IBM MQ 9.1.2 resource adapter, not an IBM MQ 9.1.2 queue manager.