Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | webMethods Messaging Administration | Configuring Administered Objects | Client Groups and Permissions | Setting Client Group Access Permissions
Setting Client Group Access Permissions
You use an administrative tool to assign access permissions to a client group.
Administrator access to a Broker Server is required to use an administrative tool, such as JMSAdmin, with that Broker Server. Administrator access is also required in order to connect to the Admin client group in the Broker that is being administered.
Typically, in the client code, after binding the administered objects to a JNDI namespace and creating the administered objects, you create the JMS and C# client groups and then assign the groups' publish and subscribe permissions for the destinations.
In the following example, JMSAdmin is used to create the client groups SampleSenders and SampleReceivers, and publish and subscribe permissions are assigned for the topic Samples::RequestInfo:

create group SampleSenders
permit group SampleSenders to publish Samples::RequestInfo
create group SampleReceivers
permit group SampleReceivers to subscribe Samples::RequestInfo
In the example, the JMSAdmin permit command adds the topic Samples::RequestInfo to the client group's can-publish and can-subscribe lists. These lists are properties of the Broker client group that stores information about which documents are authorized to be published or received.
You can also use My webMethods to create client groups and set permissions for destinations. See Administering webMethods Broker for information. This manual also contains a detailed description of the client group can-publish and can-subscribe properties.
For more information about configuring client groups and setting group permissions using JMSAdmin, see Create Group, Delete Group, Deny, and Permit.