Creating a Cluster Gateway
To link clusters with a cluster gateway, you must perform the following high-level steps:
1. Identify the list of document types that each cluster needs to receive from the other cluster and make sure that these document types exist in both clusters. If a required document type does not exist in one of the clusters, the administrator of that cluster must add it.
2. Identify the Broker pairs that will create cluster gateway connections.Make sure that each Broker in the local cluster is connected to at least one Broker in the remote cluster. 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 clusters and make sure that the Broker Servers that host the two cluster gateways support these requirements.
For example, if you want to secure each cluster gateway with an access control list (ACL), all
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 Servers that hosts their counterpart in the cluster gateway pair. For more information about SSL-enabling a
Broker Server and assigning an ACL to a cluster gateway, see
Cluster Gateway ACLs.
4. Create and configure each gateway in the cluster gateway pair. To configure a cluster gateway, you do the following:
a. Specify the local cluster, the remote cluster, and the remote Brokers that form the remote cluster.
b. Assign "Allow Receive" permission to each document type that the local cluster will receive.
c. Assign "Allow Forward" permission to each document type that the remote cluster will receive. (If necessary, you can include a filter that permits only specified instances of the document type to pass to the remote cluster.)