Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Managing Territory Gateways | Creating a Territory Gateway Connection
Creating a Territory Gateway Connection
Creating a "One-Way" Territory Gateway
To link territories with a territory gateways connection, you must to perform the following high-level steps
1. Identify the list of document types that each territory needs to receive from the other and make sure that these document types exist in both territories. If a required document type does not exist in one of the territories, the administrator of that territory must add it.
2. Identify the two Brokers that will host the territory gateways.The domain name service (DNS) used by the two host machines must be capable of bi-directional name resolution, meaning that the DNS must be able to resolve the name of the host machine to the correct IP address and also be able to resolve the machine's IP address back to the correct name.
When a host machine uses the Dynamic Host Configuration Protocol (DHCP) to dynamically obtain its IP address, many DNS servers will not return the correct name for a given IP address. In this case, you must contact your IT department or your network administrator and ask that a static IP address be assigned to the host machine.
3. Determine what type of authentication and encryption is required between the territories and make sure that the Broker Servers that host the two gateways support these requirements.
For example, if you want to secure each gateway with an access control list (ACL), both Broker Servers must be SSL-enabled (that is, have an SSL identity) and their keystores must be equipped with the trusted root and signed digital certificate for the Broker Server that hosts their counterpart in the gateway pair. For more information about SSL-enabling a Broker Server and assigning an ACL to a gateway, see Territory Gateway ACLs.
4. Create and configure each territory gateway in the gateway pair. When you configure a territory gateway, you must do the following:
a. Specify the name and location of the Broker that hosts the territory gateway in the remote territory.
b. Assign "Allow Receive" permission to each document type that the local territory needs to receive.
c. Assign "Allow Forward" permission to each document type that the remote gateway's territory needs to receive. (If necessary, you can include a filter that permits only specified instances of the document type to pass to the remote territory.)
If you control both Broker Servers, you can create and configure both territory gateways at the same time as described in Creating a Territory Gateway Pair if You Control Both Brokers. If you do not control both Broker Servers, you must create and configure your territory gateway as described in Creating a Territory Gateway Pair if You Control Only One Broker , and the administrator of the other Broker Server must create and configure its counterpart in the other territory. The territory gateway connection will not function until both gateways are configured.