Use the integral-jms-authorisations.xml file to view or change the authorization settings for Java Message Service (JMS) resources owned by the default messaging provider on WebSphere® Application Server Version 5 nodes.
Authorization to access default JMS resources owned by the default messaging provider on WebSphere Application Server nodes is controlled by the following settings in the was_install\config\cells\your_cell_name\integral-jms-authorisations.xml file.
Authorization to access default JMS resources owned by the default messaging provider on WebSphere Application Server nodes is controlled by the following settings in the wempspath/wempsname/config/integral-jms-authorizations.xml file.
<integral-jms-authorizations> <dynamic-update>true</dynamic-update> <queue-admin-userids> <userid>adminid1</userid> <userid>adminid2</userid> </queue-admin-userids> <queue-default-permissions> <permission>write</permission> </queue-default-permissions> <queue> <name>q1</name> <public> </public> <authorize> <userid>useridr</userid> <permission>read</permission> </authorize> <authorize> <userid>useridw</userid> <permission>write</permission> </authorize> </queue> <queue> <name>q2</name> <public> <permission>write</permission> </public> <authorize> <userid>useridr</userid> <permission>read</permission> </authorize> </queue> <topic> <name></name> <public> <permission>+pub</permission> </public> </topic> <topic> <name>a/b/c</name> <public> <permission>+sub</permission> </public> <authorize> <userid>useridpub</userid> <permission>+pub</permission> </authorize> </topic> </integral-jms-authorizations>
This element defines the default queue access permissions that are assumed if no permissions are specified for a specific queue name. These permissions are used for queues for which you do not define specific permissions (in queue elements). If this element is not specified, then no access permissions exist unless explicitly authorized for individual queues.
This element contains the following authorization settings for a single queue destination:
You define each default permission within a separate permission element.
You define each permission within a separate permission element. Each permission element can contain the keyword read or write to define the access permission.
<queue> <name>q1</name> <public> </public> <authorize> <userid>useridr</userid> <permission>read</permission> </authorize> <authorize> <userid>useridw</userid> <permission>write</permission> </authorize> <authorize> <userid>useridrw</userid> <permission>read</permission> <permission>write</permission> </authorize> </queue>
This element contains the following authorization settings for a single topic destination:
Each topic element has the following sub elements:
You define each default permission within a separate permission element.