Compatible configurations
Compatible connection scenarios where an IBM MQ client or queue manager communicates with MQIPT. The same or a second MQIPT route is used to communicate with a destination queue manager.
Compatible configurations with a single MQIPT route
We can use a single MQIPT route to communicate with IBM MQ.
The columns in Table 1 contain the following information:- The protocol used between IBM MQ and the MQIPT route. The connection can be created by either an IBM MQ client or queue manager, and can use either IBM MQ Formats and Protocols (FAP) or a SSL/TLS protocol.
- The mode in which the MQIPT route operates. The format of the communication across the Internet between MQIPT and IBM MQ, is determined by the configuration of the MQIPT route. Note that where the table mentions SSL, we can also use TLS.
- The protocol used between the MQIPT route and the destination queue manager.
1. IBM MQ source protocol | 2. Mode of the MQIPT route | 3. IBM MQ destination protocol |
---|---|---|
FAP | FAP-proxy (default) | FAP |
FAP-server and SSL-client | SSL/TLS | |
SSL/TLS | SSL-proxy | SSL/TLS |
SSL-server and FAP-client | FAP | |
SSL-server and SSL-client | SSL/TLS |
Compatible configurations with more than one MQIPT route
We might choose to use more than one route, on one or more instances of MQIPT, to communicate with IBM MQ.
The columns in Table 2 contain the following information:- The protocol used between IBM MQ and the first MQIPT route. The connection can be created by either an IBM MQ client or queue manager, and can use either IBM MQ Formats and Protocols (FAP) or a SSL/TLS protocol.
- The mode in which the first MQIPT route operates. The format of the communication across the Internet between MQIPT and IBM MQ, is determined by the configuration of the MQIPT route. Note that where the table mentions SSL, we can also use TLS.
- The mode in which the second MQIPT route operates.
- The protocol used between the second MQIPT route and the destination queue manager.
1. IBM MQ source protocol | 2. Mode of the first MQIPT route | 3. Mode of the second MQIPT route | 4. IBM MQ destination protocol |
---|---|---|---|
FAP (default) | FAP-proxy (default) | FAP-proxy (default) | FAP |
FAP-server and SSL-client | SSL-proxy | SSL/TLS | |
SSL-server and FAP-client | FAP | ||
SSL-server and SSL-client | SSL/TLS | ||
HTTP-client | HTTP-server and SSL-client | SSL/TLS | |
HTTPS-client | HTTPS-server and SSL-client | SSL/TLS | |
HTTP-client | HTTP-server | FAP | |
HTTPS-client | HTTPS-server | FAP | |
SSL/TLS | SSL-proxy | SSL-proxy | SSL/TLS |
SSL-server and FAP-client | FAP | ||
SSL-server and SSL-client | SSL/TLS | ||
HTTP-client | HTTP-server | FAP | |
HTTPS-client | HTTPS-server | SSL/TLS | |
HTTP-client | HTTP-server and SSL-client | FAP | |
HTTPS-client | HTTPS-server and SSL-client | SSL/TLS |