Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Securing BMC AMI Ops Automation for MQ

The following resources for IBM MQ can be secured:

  • Connections to IBM MQ
  • Access to IBM MQ objects (such as queues)
  • Use of IBM MQ system commands

This security is implemented from within the IBM MQ product. Therefore, when you want to use the BMC AMI Ops Automation for MQ component for automating IBM MQ events, you must ensure BMC AMI Ops Automation for MQ is granted the proper authority to access queue managers, system queues, and user queues as required.

BMC AMI Ops Automation for MQ does allow you to specify who has access to updating and reading Rules and scheduling EXECs. If you need to secure who has access to updating and reading Rules and EXECs for IBM MQ events, you must secure who has access to these resources. See Managing security for BMC AMI Ops products for more information.

BMC AMI Ops Automation for MQ provides the resource name:

  • prefix.ssid.AAO.target.APPL.MQSERIES

Use this resource name to secure who has access to the BMC AMI Ops Automation for MQ Workstation (described in BMC-AMI-Ops-Automation-for-MQ-automation-statistics.

For information about how to secure access to this resource, see Managing security for BMC AMI Ops products.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*