Using Client Groups to Specify Permissions on Document Types

If you have one or more client groups that identify the set of documents that a territory gateway can exchange with the remote territory, you can use those groups to specify which documents are permitted to flow to and from this territory gateway.

When you use a client group to specify the document type permissions for a territory gateway, the can-publish and can-subscribe permissions in the client group are mapped to the territory gateway permissions as follows:

This permission for a document type in the client group...	Sets this permission for the document type on the territory gateway...
Can Publish	Allow Forward (Permits the territory gateway to forward instances of the document type to subscribers in the remote territory.)
Can Subscribe	Allow Receive (Permits the territory gateway to receive instances of the document type from publishers in the remote territory.)

Important:
If you want to set permissions on both territory gateways, be sure that all of the document types in the selected client groups exist in both territories.

To use client groups to specify which document types can flow to and from a territory gateway

1. In My webMethods: Messaging > Broker Territories > Territory Gateways.

2. In the Territory Gateways List, locate the territory gateway that you want to configure and click

Details.

3. Click the Shared Document Types tab and then click Hook Up Client Groups.

4. Use the Available Client Group controls to select the client group(s) that contain the document type definitions and permissions that you want to apply to this territory gateway Broker.

5. Select one of the following options and click Update.

Enable this option...	If....
Yes. Enable Permissions on Other Side of the Gateway	You want My webMethods to automatically set the corresponding permissions for the specified document types on the remote territory gateway. (Do not use this option unless you control both territory gateways.)
No	You want to set permissions only on the local territory gateway. If you select this option, you must manually set the corresponding permissions for these document types on the remote territory gateway.