Securing WebSphere MQ Everyplace resources

If you include MQeInput or MQeOutput nodes in your message flows, consider how to control access to these resources so that:

Be aware of the security provided in each of the following areas.

WebSphere MQ Everyplace security

WebSphere MQ Everyplace security is in effect until a message sent to a WebSphere Business Integration Event Broker broker is received by the WebSphere MQ bridge queue. Up to this point, you can implement the security provided by WebSphere MQ Everyplace.

WebSphere MQ Everyplace provides security that protects message data both when held locally and when it is being transferred. Three types of protection are provided:

  • Local security provides local protection of message (and other) data.
  • Queue-based security provides protection of messages between the initiating queue manager and the target queue.
  • Message-level security provides message-level protection of messages between initiator and recipient.

This is fully documented in the WebSphere MQ Everyplace for Multiplatforms Introduction book.

WebSphere MQ security

When the message reaches the WebSphere MQ bridge queue, it is under the control of WebSphere MQ security. The information in Securing WebSphere MQ resources describes the authorizations that must be in place.

Security of output message

When the message is output from a message flow, its destination determines what security measures you must implement:

  • If the target queues are WebSphere MQ queues, follow the rules given in Securing WebSphere MQ resources.
  • If the target queues are WebSphere MQ Everyplace queues, follow the guidelines given in the WebSphere MQ Everyplace for Multiplatforms Introduction book.
Related reference
MQeInput node
MQeOutput node