Security

The queue manager fully supports the security functions supplied with WebSphere MQ Everyplace. Any messages stored in a queue defined with security characteristics are encoded using those characteristics. Any connections set up between a queue manager and a secure queue use the security characteristics of the queue, or an existing connection with equal or higher security.

Messages can be individually protected by attaching security characteristics to them directly. The correct characteristics must be presented whenever dealing with a message protected in this manner.

Connection security

Because of the way channel security works, when a specific attribute rule is specified for a target queue, it forces the local queue manager to create an instance of the same attribute rule, examples.rules.AttributeRule and com.ibm.mqe.MQeAttributeRule are treated as the same rule. If this is not a desirable behaviour, you can specify a null rule for the target queue. In this case, com.ibm.mqe.MQeAttributeDefaultRule takes effect.

See Security for a detailed discussion of WebSphere MQ Everyplace security.