Options for connecting IBM MQ classes for .NET to a queue manager

There are three modes of connecting IBM MQ classes for .NET to a queue manager. Consider which type of connection best suits we requirements.

Client bindings connection

To use IBM MQ classes for .NET as an IBM MQ MQI client, we can install it, with the IBM MQ MQI client, either on the IBM MQ server machine, or on a separate machine. A client bindings connection can use XA or non-XA transactions

Server bindings connection

When used in server bindings mode, IBM MQ classes for .NET use the queue manager API, rather than communicating through a network. This provides better performance for IBM MQ applications than using network connections.

To use the bindings connection, we must install IBM MQ classes for .NET on the IBM MQ server.

Managed client connection

A connection made in this mode connects as an IBM MQ client to an IBM MQ server running either on the local or a remote machine.

The IBM MQ classes for .NET connecting in this mode remain in .NET managed code and make no calls to native services. For more information about managed code, refer to Microsoft documentation.

There are a number of limitations to using the managed client. For more information about these, see Managed client connections.