Supported channel configurations

All IBM MQ channel types are supported, but configuration is restricted to TCP/IP connections. To an IBM MQ client or queue manager, MQIPT appears as if it is the destination queue manager. Where channel configuration requires a destination host and port number, the MQIPT host name and listener port number are specified.

Client/server channels

MQIPT listens for incoming client connection requests, and then forwards them by using either HTTP tunneling, SSL/TLS, or as standard IBM MQ protocol packets. If MQIPT is using HTTP tunneling or SSL/TLS it forwards them on a connection to a second MQIPT. If it is not using HTTP tunneling, it forwards them on a connection to what it sees as the destination queue manager (although this could in turn be a further MQIPT). When the destination queue manager has accepted the client connection, packets are relayed between client and server.

Cluster sender/receiver channels

If MQIPT receives an incoming request from a cluster-sender channel, it assumes the queue manager has been SOCKS-enabled and the true destination address will be obtained during the SOCKS handshaking process. It forwards the request to the next MQIPT or destination queue manager in exactly the same way as for client connection channels. This also includes auto-defined cluster-sender channels.

Sender/receiver

If MQIPT receives an incoming request from a sender channel, it forwards it to the next MQIPT or destination queue manager in exactly the same way as for client connection channels. The destination queue manager validates the incoming request and starts the receiver channel if appropriate. All communications between sender and receiver channel (including security flows) are relayed.

Requester/server

This combination is handled in the same manner as the preceding configurations. Validation of the connection request is performed by the server channel at the destination queue manager.

Requester/sender

The "callback" configuration could be of use if the two queue managers are not allowed to establish direct connections to each other, but are both allowed to connect to MQIPT and to accept connections from it.

Server/requester and server/receiver

These are handled by MQIPT in the same way that it handles the Sender/Receiver configuration.