Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Managing Territory Gateways | Overview
Territory Gateway Connections, Territory Gateways, and Territory Gateway Pairs
Territory Gateway Names
Connecting Multiple Territories with Territory Gateway Connections
A territory gateway connection enables two territories to exchange documents. Unlike territories, whose constituent Brokers automatically share their document types and client groups, a territory gateway connection requires an administrator to explicitly specify which document types the territories are permitted to send and receive. Moreover, the territories never share client group information.
Typically, you use a territory gateway connection when you need to share documents between two different application or administrative domains. For example, in a configuration where one territory handles documents relating to employee records and another territory handles documents relating to IT resources, the IT territory might need to receive certain documents relating to employee start, exit, or transfer events. To enable these documents to travel to the IT territory, you can link the territories using a territory gateway connection.
You can also use a territory gateway connection to link identical territories that are geographically separated. For example, if you have a territory that handles documents relating to manufacturing operations in North America and you expand the application to operations in Asia, you might decide to create an identical territory for the Asian region and then link the territories using a territory gateway connection. In this case, you are using a gateway to conserve wide-area network bandwidth by explicitly restricting what document types can flow across the network link.