MQ

Hi,
I have CP4I 2021.3 installed on OCP 4.8.17.  I created a quickstart local QMgr and Q using the platform navigator.  The connection file generated indicates to use port 443.  Using an MQ client I am unable to connect to the QMgr.  The service and route on OCP indicate port 1414.  The only active listener shown in the platform navigator is on port 1414.  On the server where OCP is running, there is nothing listening on port 1414.  From my client machine I can net-connect to the MQ host name using port 443, but I do not see any MQ related listeners on the server for port 443. What is needed to enable an MQ Client to connect to the QMgr?

------------------------------
Lawrence Norcini
Lilburn GA
------------------------------

Hi,  If you are using the MQ operator then it will setup a QMGR that listens on 1414, the service will route requests to the QMGR and the Route, which is on 443, will route the requests to the service.  To access the QMGR externally, you need to create a new route for the channel that you want to use and then have your client connect to the MQ Route on port 443.  You can look at my example.  

Brian

------------------------------
Brian S Paskin
Sr. Web Engineer
IBM Tech Garage
------------------------------

Original Message:
Sent: Fri December 17, 2021 03:24 PM
From: Lawrence Norcini
Subject: MQ on CP4I

Hi,
I have CP4I 2021.3 installed on OCP 4.8.17.  I created a quickstart local QMgr and Q using the platform navigator.  The connection file generated indicates to use port 443.  Using an MQ client I am unable to connect to the QMgr.  The service and route on OCP indicate port 1414.  The only active listener shown in the platform navigator is on port 1414.  On the server where OCP is running, there is nothing listening on port 1414.  From my client machine I can net-connect to the MQ host name using port 443, but I do not see any MQ related listeners on the server for port 443. What is needed to enable an MQ Client to connect to the QMgr?

------------------------------
Lawrence Norcini
Lilburn GA
------------------------------

Thanks for this.  I created the QMgr and everything else using the platform navigator.  I already have an external-tls-secret  in the cp4i namespace.  The hostname in my route is quickstart-cp4i-ibm-mq-qm-cp4i.apps.lnlcluster.ibm-cp4-dojo.net.  The SNI name would be something like: 71-75-69-63-6b-73-74-61-72-74-2d-63-70-469-2d-6d-71-2d-71-6d-2d-63-70-469-2e-61-70-70-73-2e-6c-6e-6c-63-6c-75-73-74-65-72-2e-69-62-6d-2d-63-70-42d-64-6f-6a-6f-2e-6e-65-74-

This is the connection information I get from the Platform Navigator:
{
"channel": [
{
"name": "MQ.QS.SVRCONN",
"clientConnection": {
"connection": [
{
"host": "quickstart-cp4i-ibm-mq-qm-cp4i.apps.lnlcluster.ibm-cp4-dojo.net",
"port": 443
}
],
"queueManager": "QUICKSTART"
},
"type": "clientConnection"
}
]
}
So my question is, what route do I need to define?

------------------------------
Lawrence Norcini
Lilburn GA
------------------------------

Original Message:
Sent: Mon December 20, 2021 03:49 AM
From: Brian S Paskin
Subject: MQ on CP4I

Hi,  If you are using the MQ operator then it will setup a QMGR that listens on 1414, the service will route requests to the QMGR and the Route, which is on 443, will route the requests to the service.  To access the QMGR externally, you need to create a new route for the channel that you want to use and then have your client connect to the MQ Route on port 443.  You can look at my example.  

Brian

------------------------------
Brian S Paskin
Sr. Web Engineer
IBM Tech Garage

Original Message:
Sent: Fri December 17, 2021 03:24 PM
From: Lawrence Norcini
Subject: MQ on CP4I

Hi,
I have CP4I 2021.3 installed on OCP 4.8.17.  I created a quickstart local QMgr and Q using the platform navigator.  The connection file generated indicates to use port 443.  Using an MQ client I am unable to connect to the QMgr.  The service and route on OCP indicate port 1414.  The only active listener shown in the platform navigator is on port 1414.  On the server where OCP is running, there is nothing listening on port 1414.  From my client machine I can net-connect to the MQ host name using port 443, but I do not see any MQ related listeners on the server for port 443. What is needed to enable an MQ Client to connect to the QMgr?

------------------------------
Lawrence Norcini
Lilburn GA
------------------------------

Hi, So your channel name would be :

mq2e-qs2e-svrconn.chl.mq.ibm.com

example:

apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: quickstart-ibm-mq-traffic
spec:
  host: mq2e-qs2e-svrconn.chl.mq.ibm.com
  to:
    kind: Service
    name: quickstart-ibm-mq
  port:
    targetPort: 1414
  tls:
    termination: passthrough

------------------------------
Brian S Paskin
Sr. Web Engineer
IBM Tech Garage
------------------------------

Original Message:
Sent: Mon December 20, 2021 11:26 AM
From: Lawrence Norcini
Subject: MQ on CP4I

Thanks for this.  I created the QMgr and everything else using the platform navigator.  I already have an external-tls-secret  in the cp4i namespace.  The hostname in my route is quickstart-cp4i-ibm-mq-qm-cp4i.apps.lnlcluster.ibm-cp4-dojo.net.  The SNI name would be something like: 71-75-69-63-6b-73-74-61-72-74-2d-63-70-469-2d-6d-71-2d-71-6d-2d-63-70-469-2e-61-70-70-73-2e-6c-6e-6c-63-6c-75-73-74-65-72-2e-69-62-6d-2d-63-70-42d-64-6f-6a-6f-2e-6e-65-74-

This is the connection information I get from the Platform Navigator:
{
"channel": [
{
"name": "MQ.QS.SVRCONN",
"clientConnection": {
"connection": [
{
"host": "quickstart-cp4i-ibm-mq-qm-cp4i.apps.lnlcluster.ibm-cp4-dojo.net",
"port": 443
}
],
"queueManager": "QUICKSTART"
},
"type": "clientConnection"
}
]
}
So my question is, what route do I need to define?

------------------------------
Lawrence Norcini
Lilburn GA

Original Message:
Sent: Mon December 20, 2021 03:49 AM
From: Brian S Paskin
Subject: MQ on CP4I

Hi,  If you are using the MQ operator then it will setup a QMGR that listens on 1414, the service will route requests to the QMGR and the Route, which is on 443, will route the requests to the service.  To access the QMGR externally, you need to create a new route for the channel that you want to use and then have your client connect to the MQ Route on port 443.  You can look at my example.  

Brian

------------------------------
Brian S Paskin
Sr. Web Engineer
IBM Tech Garage

Original Message:
Sent: Fri December 17, 2021 03:24 PM
From: Lawrence Norcini
Subject: MQ on CP4I

Hi,
I have CP4I 2021.3 installed on OCP 4.8.17.  I created a quickstart local QMgr and Q using the platform navigator.  The connection file generated indicates to use port 443.  Using an MQ client I am unable to connect to the QMgr.  The service and route on OCP indicate port 1414.  The only active listener shown in the platform navigator is on port 1414.  On the server where OCP is running, there is nothing listening on port 1414.  From my client machine I can net-connect to the MQ host name using port 443, but I do not see any MQ related listeners on the server for port 443. What is needed to enable an MQ Client to connect to the QMgr?

------------------------------
Lawrence Norcini
Lilburn GA
------------------------------

Please note that you must have TLS enabled on the QMGR for this to work.  In your CCDT it is lacking the necessary TLS cipher elements.

Brian

------------------------------
Brian S Paskin
Sr. Web Engineer
IBM Tech Garage
------------------------------

Original Message:
Sent: Tue December 21, 2021 01:34 AM
From: Brian S Paskin
Subject: MQ on CP4I

Hi, So your channel name would be :

mq2e-qs2e-svrconn.chl.mq.ibm.com

example:

apiVersion: route.openshift.io/v1kind: Routemetadata:  name: quickstart-ibm-mq-trafficspec:  host: mq2e-qs2e-svrconn.chl.mq.ibm.com  to:    kind: Service    name: quickstart-ibm-mq  port:    targetPort: 1414  tls:    termination: passthrough

------------------------------
Brian S Paskin
Sr. Web Engineer
IBM Tech Garage

Original Message:
Sent: Mon December 20, 2021 11:26 AM
From: Lawrence Norcini
Subject: MQ on CP4I

Thanks for this.  I created the QMgr and everything else using the platform navigator.  I already have an external-tls-secret  in the cp4i namespace.  The hostname in my route is quickstart-cp4i-ibm-mq-qm-cp4i.apps.lnlcluster.ibm-cp4-dojo.net.  The SNI name would be something like: 71-75-69-63-6b-73-74-61-72-74-2d-63-70-469-2d-6d-71-2d-71-6d-2d-63-70-469-2e-61-70-70-73-2e-6c-6e-6c-63-6c-75-73-74-65-72-2e-69-62-6d-2d-63-70-42d-64-6f-6a-6f-2e-6e-65-74-

This is the connection information I get from the Platform Navigator:
{
"channel": [
{
"name": "MQ.QS.SVRCONN",
"clientConnection": {
"connection": [
{
"host": "quickstart-cp4i-ibm-mq-qm-cp4i.apps.lnlcluster.ibm-cp4-dojo.net",
"port": 443
}
],
"queueManager": "QUICKSTART"
},
"type": "clientConnection"
}
]
}
So my question is, what route do I need to define?

------------------------------
Lawrence Norcini
Lilburn GA

Original Message:
Sent: Mon December 20, 2021 03:49 AM
From: Brian S Paskin
Subject: MQ on CP4I

Hi,  If you are using the MQ operator then it will setup a QMGR that listens on 1414, the service will route requests to the QMGR and the Route, which is on 443, will route the requests to the service.  To access the QMGR externally, you need to create a new route for the channel that you want to use and then have your client connect to the MQ Route on port 443.  You can look at my example.  

Brian

------------------------------
Brian S Paskin
Sr. Web Engineer
IBM Tech Garage

Original Message:
Sent: Fri December 17, 2021 03:24 PM
From: Lawrence Norcini
Subject: MQ on CP4I

Hi,
I have CP4I 2021.3 installed on OCP 4.8.17.  I created a quickstart local QMgr and Q using the platform navigator.  The connection file generated indicates to use port 443.  Using an MQ client I am unable to connect to the QMgr.  The service and route on OCP indicate port 1414.  The only active listener shown in the platform navigator is on port 1414.  On the server where OCP is running, there is nothing listening on port 1414.  From my client machine I can net-connect to the MQ host name using port 443, but I do not see any MQ related listeners on the server for port 443. What is needed to enable an MQ Client to connect to the QMgr?

------------------------------
Lawrence Norcini
Lilburn GA
------------------------------