Setting a Primary Connection for the Cluster Gateway Broker. You set the "primary connection" to designate a default gateway connection that the local Broker and remote Broker must use to route messages between themselves across the gateway. For more information about setting the primary gateway connection, see Editing Cluster Gateway Details.

Pausing and Resuming a Cluster Gateway. The pause and resume controls enable you to stop the flow of outbound traffic from a cluster gateway to the remote cluster. For more information about using these controls, see Pausing and Resuming a Cluster Gateway.

Configuring the Keep-Alive Setting. The keep-alive setting instructs the local gateway Brokers to issue periodic "keep-alive" messages to the remote gateway Brokers. You use this option if the cluster gateway connects through a firewall that automatically drops connections that are idle for an extended period. For more information about using the keep-alive feature, see Preventing Connection Timeouts between Clusters.

Configuring the Forwarding Mode. The forwarding mode determines how a cluster gateway maintains the subscription list for the remote cluster. For more information about specifying the forwarding mode, see Configuring the Forwarding Mode.

Blocking Document Type Updates. By default, any change made to a document type permitted for exchange between two clusters will be updated synchronously in both the clusters. You can use the "refuse update" option to suppress this behavior on one or both cluster gateways. For information about blocking updates, see Refusing Document Type Updates from a Remote Cluster Gateway.