I am not sure I agree with your conclusion, as WMQ supported SSL V3.0 and TLS V1.0 since at least V6.0 and, possibly, earlier. It is rather a configuration mismatch between the client and server. The recommended procedure for resolving SSL / TLS problems is as follows:
My method for debugging SSL connections in WMQ should go through the following sequence so that each step works before moving on to the next:
- Get a channel without SSL. This confirms that the channel names are spelled correctly, that there is a QMgr listener between the endpoints, and that the client points to the right port. You would be surprised how many times someone incorrectly enters a port or channel name.
- , SVRCONN,
SSLCAUTH(OPTIONAL). SSL-, , . QMgr , . , QMgr QMgr. (: QMgr , , . , , . . !) - SVRCONN
SSLCAUTH(REQUIRED). , ( ) . , QMgr . - SSLPEER CHLAUTH, , .
№ 2 №3 SSL . , . .
UPDATE
. , SSL/TLS. , . - , . . ( CA) . . , Java JMS JSSE , . Java JMS , .
WebSphere MQ, Java, . kdb, CMS, , KDB. " " . .Net SSL MQEnviornment.
SSL/TLS . , , , . , , ( -), , . , , , , .
2, , . QMgr . QMgr , AMQERR01.LOG. QMgr, 2!
QMgr , , , . , , . , , , .kdb. , QMgr [keystorename].kdb.kdb, . , , . -Java- WMQ , ibmwebspheremq, . , TRob, ibmwebspheremqtrob. , .
Windows, MQ . , WMQ .