WCF Connection options

There are three modes of connecting an IBM MQ custom channel for WCF to a queue manager. Consider which type of connection best suits we requirements.

For more information about connection options, see: Connection differences

For more information about WCF architecture, see: WCF architecture

Unmanaged client connection

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

To use the IBM MQ custom channel for WCF as an IBM MQ client, we can install it, with the IBM MQ MQI client, either on the IBM MQ server, or on a separate machine.

Unmanaged server connection

When used in server bindings mode, the IBM MQ custom channel for WCF uses the queue manager API, rather than communicating through a network. Using bindings connections provides better performance for IBM MQ applications than using network connections.

To use the bindings connection, we must install the IBM MQ custom channel for WCF 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 machine or on a remote machine.

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

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