Use IBM MQ classes for XMS .NET Standard

From Version 9.2.0, IBM MQ classes for XMS .NET Standard, including samples, are installed with IBM MQ on Windows and Linux . There is a prerequisite of Microsoft.NET Core for IBM MQ classes for XMS .NET Standard.

From IBM MQ Version 9.2.0, Microsoft.NET Core 3.1 is the minimum required version for running IBM MQ classes for XMS .NET Standard.


amqmxmsstd.dll library

From Version 9.2.0, the IBM MQ classes for XMS .NET Standard library, amqmxmsstd.dll, is available for XMS .NET Standard support on Windows and Linux.

The XMS .NET samples are located in &MQINSTALL_PATH&/samp/dotnet/samples/cs/core/xms.

The library is installed into /&MQINSTALL_PATH&/lib64 path when an IBM MQ client is installed on Linux.

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

Attention: All the IBM.XMS.* libraries are still supplied, but these libraries are stabilized; that is, no new features will be introduced into them.

For any of the latest features, we must migrate to the amqmxmsstd.dll library. However, we can continue to use the existing libraries on IBM MQ Version 9.1 Long Term Support or Continuous Delivery releases.

From Version 9.2.0, the IBM MQ classes for XMS .NET Standard are available for downloading from the NuGet repository. The NuGet package contains both the amqmxmsstd.dll library and the amqmdnetstd.dll library. For more information, see Downloading IBM MQ classes for XMS .NET Standard from the NuGet repository.


dspmqver command

We can use the dspmqver command to display version and build information for the .NET Core component.


IBM MQ classes for XMS .NET Framework and IBM MQ classes for XMS .NET Standard features

The following table lists the features for IBM MQ classes for XMS .NET Framework compared with the features for IBM MQ classes for XMS .NET Standard.

Feature IBM MQ classes for XMS .NET Framework IBM MQ classes for XMS .NET Standard
Class Names (APIs) All classes remain the same in each network. All classes remain the same in each network.
Operate System Windows Windows
Dockerized containers

Linux

MacOS
app.config file (Configuration file to enable Trace in redistributable client) app.config file is used to enable trace for the redistributable package app.config is not supported in .NET Standard.

We have to use environment variables in place of app.config.
Trace The strmqtrc command and, for redistributable clients, the app.config file, are used to enable trace. To trace the XMS .NET client on .NET Standard, we need to use the strmqtrc command, and the existing environment variables, such as the environment variable XMS_TRACE_ON used to enable trace. For more information, see Configure XMS .NET trace using XMS environment variables.
Transport Modes Managed, Unmanaged, and Bindings Managed
TLS The Windows keystore is used for storing the certificates.

On Windows, the keystore must be used for storing the certificates. Permitted values are *USER or *SYSTEM. Based on the input, the IBM MQ .NET client looks at the Windows key store of the current user, or System wide.

On Linux, it is recommended to use the X509Store class to install certificates and .NET Core installs certificates to the following location: ".dotnet/corefx/cryptography/x509stores".
CCDT Supported Supported, and the settings of the CCDT path are the same as for .NET Framework classes.
Client auto reconnect Supported Supported
Distributed transactions Supported Not supported
Installation of dynamic linked libraries (dll's) into the global assembly cache (GAC) Dll's are installed into the GAC as part of the IBM MQ installation. Dll's are not installed into the GAC as part of the IBM MQ installation.
Support for WMQ, WPM, and RTT connection types Supports WMQ, WPM, and RTT connection types Support for WMQ only
JNDI administered objects Supports LDAP and FileSystem Supports FileSystem only

Parent topic: Set up the messaging server environment


Related tasks