![How to grant access to view JMS messages in Weblogic issues-after-qlikview-version-upgrade-on-passive-node-of-production-servers](https://www.s-squaresystems.com/wp-content/uploads/How-to-grant-access-to-view-JMS-messages-in-Weblogic.png)
Login to Admin console and navigate to JMX Policy Editor Page.
Console -> Security Realms -> myrealm -> Roles and Policies -> Realm Policies -> Click on “JMX Policy Editor”.
![Picture85](https://www.s-squaresystems.com/wp-content/uploads/Picture85.jpg)
-
- Select “Global Scope” and click “Next”.
![Picture86](https://www.s-squaresystems.com/wp-content/uploads/Picture86.jpg)
-
- Expand “weblogic.management.runtime”, select“JMSDestinationRuntimeMBean“and click next.
![Picture87](https://www.s-squaresystems.com/wp-content/uploads/Picture87.jpg)
-
- In Attributes and Operations, select“Operations: Permission to Invoke”. Click on “Create Policy”
- In Attributes and Operations, select“Operations: Permission to Invoke”. Click on “Create Policy”
![Picture88](https://www.s-squaresystems.com/wp-content/uploads/Picture88.jpg)
-
- Click on“Add Condition”-> Select “User” in “Predicate List” -> click next -> type User Argument Name (Username for which you want to provide access) -> click “add” and then “Finish”.
- Click on“Add Condition”-> Select Role in “Predicate List” -> click next -> type Role Argument Name (Admin) -> click “add” and then “Finish”.
![Picture89](https://www.s-squaresystems.com/wp-content/uploads/Picture89.jpg)
-
- User should now be able to access JMS messages.
Note: If you do not see “JMX Policy Editor” option, it means that realm hasn’t been configured to delegate MBean authorization.