Verify task 1

 

We can issue some DISPLAY commands to verify that the task has been completed successfully. If the task was successful, the resulting output will be similar to that shown in the following examples.

From the QM1 queue manager, enter the following command:

DISPLAY CHS(QM1.TO.QM2) SSLPEER SSLCERTI
The resulting output will be similar to the following:
dis chs(QM1.TO.QM2) SSLPEER SSLCERTI
     4 : dis chs(QM1.TO.QM2) SSLPEER SSLCERTI
AMQ8417: Display Channel Status details.
   CHANNEL(QM1.TO.QM2)                     CHLTYPE(SDR)
   CONNAME(9.20.25.40)                     CURRENT
   RQMNAME(QM2)
   SSLCERTI(CN=QM2,OU="WebSphere MQ Development",O=IBM,ST=Hampshire,C=UK)
   SSLPEER(CN=QM2,OU="WebSphere MQ Development",O=IBM,ST=Hampshire,C=UK)
   STATUS(RUNNING)                         SUBSTATE(MQGET)
   XMITQ(QM2)

From the QM2 queue manager, enter the following command:

DISPLAY CHS(QM1.TO.QM2) SSLPEER SSLCERTI
The resulting output will be similar to the following:
dis chs(QM1.TO.QM2) SSLPEER SSLCERTI
     5 : dis chs(QM1.TO.QM2) SSLPEER SSLCERTI
AMQ8417: Display Channel Status details.
   CHANNEL(QM2.TO.QM1)                     CHLTYPE(RCVR)
   CONNAME(9.20.35.92)                     CURRENT
   RQMNAME(QM1)
   SSLCERTI(CN=QM1,OU="WebSphere MQ Development",O=IBM,ST=Hampshire,C=UK
   SSLPEER(CN=QM1,OU="WebSphere MQ Development",O=IBM,ST=Hampshire,C=UK)
   STATUS(RUNNING)                         SUBSTATE(RECEIVE)
   XMITQ( )

In each case, the value of SSLPEER should match that of the DN in the partner certificate that was created in Step 2. The issuer’s name matches the peer name because this is a self-signed certificate.

SSLPEER is optional. If it is specified, its value must be set so that the DN in the partner certificate (created in step 2) is allowed. For more information on the use of SSLPEER, see WebSphere MQ rules for SSLPEER values.

 

Parent topic:

Task 1: Using self-signed certificates


sy11700_