<commit_before>-   [Home](../../index.md)
-   [Documentation](../index.md)
-   Configure Enterprise Shield&trade; in a Cluster?

Configure Enterprise Shield&trade; in a Cluster ![This feature is available in KAAZING Gateway - Enterprise Edition](images/enterprise-feature.png)
===================================================================================

To add Enterprise Shield&trade; to your cluster configuration, you can start out by following the guidelines described in the [Configure Enterprise Shield&trade;](p_rc_config.md) topic. After that, the key is to configure Enterprise Shield&trade; on each cluster member, and create an equivalent number of cluster members on the DMZ and the trusted network.

In Figure 1, there are three Gateways running in the DMZ and a matching set of three Gateways on the trusted network. Thus, each internal Gateway is paired to one explicit cluster member in the DMZ.

<figure style="margin-left:0px;">
![Gateway Topology Showing Reverse Connectivity in a Cluster](../images/f-dmz-trustednetwork-860-07.png)
<figcaption>
**Figure 1: Gateway Topology Configured for Enterprise Shield&trade; in a Cluster**
</figcaption>
</figure>
Note that Enterprise Shield&trade; does not affect the behavior of the cluster in any way. Clients initiate requests in the same way and are unaware that the cluster is configured for reverse connectivity. You connect with a client in the same way as you would for a cluster without Enterprise Shield&trade;.

The recommended method of setting up Enterprise Shield&trade; in a cluster is as follows:

-   Configure a reverse connection on each cluster member.</a>
-   Use pairing (or coupling) to match up each cluster member on the DMZ with a cluster member on the trusted network.

    To pair cluster members you configure the HTTP transport identically on the internal Gateway and DMZ Gateway. For example, to configure the six Gateways shown in Figure 1:

    **Gateway Cluster Pair 1**

    On the first DMZ Gateway, configure the `connect-options` as follows:

    ``` auto-links:
               <http.transport>
                 socks+ssl://gateway1.dmz.net:1080
               </http.transport>
    ```

    On the first internal Gateway, configure the `accept-options` as follows:

    ``` auto-links:
               <http.transport>
                 socks+ssl://gateway1.dmz.net:1080
               </http.transport>
    ```

    **Gateway Cluster Pair 2**

    On the second DMZ Gateway, configure the `connect-options` as follows:

    ``` auto-links:
               <http.transport>
                 socks+ssl://gateway2.dmz.net:1080
               </http.transport>
    ```

    On the second internal Gateway, configure the `accept-options` as follows:

    ``` auto-links:
               <http.transport>
                 socks+ssl://gateway2.dmz.net:1080
               </http.transport>
    ```

    **Gateway Cluster Pair 3**

    On the third DMZ Gateway, configure the `connect-options` as follows:

    ``` auto-links:
               <http.transport>
                 socks+ssl://gateway3.dmz.net:1080
               </http.transport>
    ```

    On the third internal Gateway, configure the `accept-options` as follows:

    ``` auto-links:
               <http.transport>
                 socks+ssl://gateway3.dmz.net:1080
               </http.transport>
    ```

See Also
--------

-   [About Enterprise Shield&trade;](o_rc_checklist.md#whatis)
-   [Configure Enterprise Shield&trade;](p_rc_config.md)
-   [Configure the Gateway for High Availability](../high-availability/o_ha.md)
-   [Cluster Reference](../admin-reference/r_conf_cluster.md)


<commit_msg>Update p_rc_cluster.md<commit_after>-   [Home](../../index.md)
-   [Documentation](../index.md)
-   Configure Enterprise Shield&trade; in a Cluster?

Configure Enterprise Shield&trade; in a Cluster ![This feature is available in KAAZING Gateway - Enterprise Edition](images/enterprise-feature.png)
===================================================================================

To add Enterprise Shield&trade; to your cluster configuration, you can start out by following the guidelines described in the [Configure Enterprise Shield&trade;](p_rc_config.md) topic. After that, the key is to configure Enterprise Shield&trade; on each cluster member, and create an equivalent number of cluster members on the DMZ and the trusted network.

In Figure 1, there are three Gateways running in the DMZ and a matching set of three Gateways on the trusted network. Thus, each internal Gateway is paired to one explicit cluster member in the DMZ.

![Gateway Topology Showing Reverse Connectivity in a Cluster](../images/f-dmz-trustednetwork-860-07.png)
**Figure 1: Gateway Topology Configured for Enterprise Shield&trade; in a Cluster**

Note that Enterprise Shield&trade; does not affect the behavior of the cluster in any way. Clients initiate requests in the same way and are unaware that the cluster is configured for reverse connectivity. You connect with a client in the same way as you would for a cluster without Enterprise Shield&trade;.

The recommended method of setting up Enterprise Shield&trade; in a cluster is as follows:

-   Configure a reverse connection on each cluster member.
-   Use pairing (or coupling) to match up each cluster member on the DMZ with a cluster member on the trusted network.

    To pair cluster members you configure the HTTP transport identically on the internal Gateway and DMZ Gateway. For example, to configure the six Gateways shown in Figure 1:

    **Gateway Cluster Pair 1**

    On the first DMZ Gateway, configure the `connect-options` as follows:

    ``` xml
    <http.transport>
         socks+ssl://gateway1.dmz.net:1080
    </http.transport>
    ```

    On the first internal Gateway, configure the `accept-options` as follows:

    ``` xml
    <http.transport>
        socks+ssl://gateway1.dmz.net:1080
    </http.transport>
    ```

    **Gateway Cluster Pair 2**

    On the second DMZ Gateway, configure the `connect-options` as follows:

    ``` xml
    <http.transport>
        socks+ssl://gateway2.dmz.net:1080
    </http.transport>
    ```

    On the second internal Gateway, configure the `accept-options` as follows:

    ``` xml
    <http.transport>
        socks+ssl://gateway2.dmz.net:1080
    </http.transport>
    ```

    **Gateway Cluster Pair 3**

    On the third DMZ Gateway, configure the `connect-options` as follows:

    ``` xml
    <http.transport>
        socks+ssl://gateway3.dmz.net:1080
    </http.transport>
    ```

    On the third internal Gateway, configure the `accept-options` as follows:

    ``` xml
    <http.transport>
        socks+ssl://gateway3.dmz.net:1080
    </http.transport>
    ```

See Also
--------

-   [About Enterprise Shield&trade;](o_rc_checklist.md#about-enterprise-shield)
-   [Configure Enterprise Shield&trade;](p_rc_config.md)
-   [Configure the Gateway for High Availability](../high-availability/o_ha.md)
-   [Cluster Reference](../admin-reference/r_conf_cluster.md)

{'fraction_non_alphanumeric': 0.11572826549425613, 'fraction_numerical': 0.011771379946106934, 'mean_word_length': 3.237980769230769, 'pattern_counts': {'":': 0, '<': 32, '<?xml version=': 0, '>': 32, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 6}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6802208', 'n_tokens_mistral': 2007, 'n_tokens_neox': 1821, 'n_words': 734}