Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Managing Territory Gateways | Overview | Territory Gateway Connections, Territory Gateways, and Territory Gateway Pairs
Territory Gateway Connections, Territory Gateways, and Territory Gateway Pairs
The term territory gateway connection refers to the link that enables two territories to exchange documents. To create this link, two Brokers, one from each territory, are designated to communicate with one another. To form a territory gateway connection, you must create and configure a gateway on each of these Brokers.
A territory gateway performs functions similar to those performed by a Remote Broker object in a territory. In this capacity, the territory gateway:
*Establishes and maintains a connection with its counterpart in the remote territory
*Maintains the subscription list and forward queue for the remote territory
*Retrieves documents for the local territory from the remote gateway
Unlike a Remote Broker object, however, a territory gateway requires an administrator to explicitly specify which document types it can "forward to" and "receive from" the remote territory. The territory gateway enforces these permissions on the documents that pass through it.
The Broker that hosts a territory gateway is a regular member of its own territory and can handle regular clients in addition to the territory gateway.
Collectively, the two territory gateways that operate together to form a territory gateway connection are known as a gateway pair. A territory gateway connection will not function until both Brokers have been equipped with a territory gateway and both territory gateways in the pair are configured correctly.