Disabling Advanced Message Security at the client
You need to disable IBM® MQ Advanced Message Security (AMS) if you are using an IBM WebSphere® MQ 7.5 or later client to connect to a queue manager from an earlier version of the product and a 2085 (MQRC_UNKNOWN_OBJECT_NAME) error is reported.
About this task
From IBM WebSphere MQ 7.5, IBM MQ Advanced Message Security (AMS) is automatically enabled in an IBM MQ client and so, by default, the client tries to check the security policies for objects at the queue manager. However, servers on earlier versions of the product, for example IBM WebSphere MQ 7.1, do not have AMS enabled and this causes 2085 (MQRC_UNKNOWN_OBJECT_NAME) error to be reported.
- For Java clients, in any of the following ways:
- By setting an environment variable AMQ_DISABLE_CLIENT_AMS.
- By setting the Java system property com.ibm.mq.cfg.AMQ_DISABLE_CLIENT_AMS.
- By using the DisableClientAMS property, under the Security stanza in the mqclient.ini file.
- For C clients, in either of the following ways:
- By setting an environment variable MQS_DISABLE_ALL_INTERCEPT.
- By using the DisableClientAMS property, under the Security stanza in the mqclient.ini file.
Procedure
- AMQ_DISABLE_CLIENT_AMS environment variable
- You need to set this variable in the following cases:
- If you are using Java Runtime Environment (JRE) other than the IBM Java Runtime Environment (JRE)
- If you are using IBM WebSphere MQ 7.5, or later IBM MQ classes for JMS or IBM MQ classes for Java client.
- Java system property com.ibm.mq.cfg.AMQ_DISABLE_CLIENT_AMS
- For IBM MQ classes for JMS and IBM MQ classes for Java clients, you can set the Java system property com.ibm.mq.cfg.AMQ_DISABLE_CLIENT_AMS to the value TRUE for the Java application.
- MQS_DISABLE_ALL_INTERCEPT environment variable
- You need to set this variable if you are using IBM MQ 8.0 or later with native clients and you need to disable AMS at the client.
- DisableClientAMS property in the mqclient.ini file
- You can use this option for IBM MQ classes for JMS and IBM MQ classes for Java clients, and for C clients.
What to do next
For more information on problems with opening AMS protected queues, see Problems opening protected queues when using JMS.