As mentioned in Part 1, there are restrictions and limitations with any super cluster topology.
如第1部分所述，任何超级集群拓扑结构都存在限制和局限性。
For this example, if you have completed that task, then you're ready to distribute client requests across the super cluster.
对于本例，如果您已经完成了映射任务，那么现在就可以开始在超级集群间分发客户机请求了。
As mentioned earlier, various kinds of routers can be used in a super cluster topology.
如前所述，在超级集群拓扑结构中可以使用各种各样的路由器。
All super cluster options have some limitations, but the restrictions might be appropriate depending on the given scenario.
所有超级集群选项都存在某些限制，但是对于给定的场景，这些限制可能是必要的。
For these scenarios, one technique that can be used to overcome the implicit cluster size limit is to define a hierarchical cluster or "super cluster," as shown in Figure 1.
对于这些情况，可以用来克服这种潜在的集群大小限制的技巧就是定义一个具有层次结构的集群，即“超级集群”，如图1所示。
The proxy server will automatically route HTTP requests to all members of the super cluster, while maintaining session affinity.
代理服务器将自动把HTTP请求路由到超级集群中的所有成员，同时维护会话的亲缘性。
There are restrictions and limitations with any super cluster topology.
任何超级集群拓扑结构都具有局限性。
In a super cluster topology, you must edit this static routing information to make a single flattened cluster that contains all of the members of the super cluster.
在超级集群拓扑结构中，必须编辑这个静态路由信息来生成一个单一的扁平式集群，其中包含超级集群的所有成员。
The principle of the super cluster depends heavily on the request forwarding capabilities of various routers involved in the topologies.
超级集群的原理主要依赖于拓扑结构中涉及的各种路由器的请求转发能力。
Now, let’s examine some reasons why you might want to use of both types of routers together with your super cluster topology.
现在，让我们看看在什么情况下需要对超级集群拓扑结构结合使用这两种路由器类型。
Congratulations, you now have a proxy server distributing requests across a super cluster!
祝贺您，您现在已经可以使用代理服务器在超级集群间分发请求了。
The best way to understand how a secure proxy can be used to route requests across a super cluster is to look at a simple example.
要理解如何使用安全代理在超级集群之间路由请求，最好的办法是查看一个简单的示例。
The members of the proxy cluster forward requests to the members of the super cluster.
代理集群的成员将把请求转发给超级集群的成员。
The need for a super cluster does not occur in everyday practice, but should it happen for HTTP clients or large WebSphere eXtreme Scale grids, there are ways you can address it.
日常实践用不到超级集群，但是，对于HTTP客户机或大型WebSphereeXtremeScale网格，确实存在这方面的需求，您可以使用多种方法来解决这个问题。
There is no theoretical limit on the number WebSphere Application Server instances a super cluster can contain, but the super clustering technique should not be considered a panacea for scalability.
从理论上讲，超级集群可以包含的WebSphereApplicationServer实例的数量没有限制，但是超级集群技巧不应该作为实现可伸缩性的万能解决方案。
Though there is no theoretical limit on the number WebSphere Application Server instances a super cluster can contain, super clustering should not be considered as a panacea for scalability.
尽管在理论上并没有限制超级集群可以容纳的WebSphereApplicationServer实例的数量，但是不应该将超级集群视为实现可伸缩性的万能解决方案。
For uniform load balancing across all the members of the super cluster, you can change the LoadBalanceWeight attributes of the super cluster members.
要在超级集群的所有成员之间实现均衡的负载平衡，可以修改超级集群成员的loadbalanceweight属性。
The need for a super cluster does not occur in everyday practice, but should it happen for HTTP clients, it can be addressed.
对超级集群的需求并不会出现在日常的实践中，但是它会出现在HTTP客户机中，这种需求可以得到满足。
Notice the similarity of this topology with the topology described in Part 1 for using both the HTTP plug-in and proxy servers with a super cluster.
注意这个拓扑结构与第 1部分描述的拓扑结构的相似性，后者对超级集群同时使用了HTTP插件和代理服务器。
All super cluster options have some limitations, but the restrictions might very well be appropriate, depending on the scenario.
所有超级集群都存在某种限制，但是根据具体的场景，某些限制可能是非常有必要的。
Unlike application deployment in a traditional cluster, application deployment in a super cluster is not necessarily a one step process, and can be a multi-step process.
与传统集群中的应用程序部署不同，超级集群中的应用程序部署并不是一个单步过程，而是涉及到多个步骤。
So far, you have seen how to configure a super cluster topology when the router is either the HTTP plug-in or the proxy server.
目前为止，您已经了解了在使用HTTP插件或代理服务器作为路由器时如何配置超级集群拓扑结构。
For these scenarios, one technique that can be used to overcome the implicit cluster size limit is to define a super cluster or "cluster-of-clusters" topology.
对于这些场景，可以使用一种技巧来解决这种隐含的集群大小限制，那就是定义一个超级集群或“集群式集群”的拓扑结构。
Using a proxy server with a super cluster topology is convenient because there is no need to manually edit and administer a static route configuration file.
对超级集群拓扑结构使用代理服务器将十分方便，因为不需要手动编辑或管理静态路由配置文件。
The type of router that is used to distribute client requests directly influences the use of a super cluster and its associated limitations.
用于分发客户机请求的路由器的类型直接影响超级集群的应用和相关限制。
This will allow you to use the heap space of all the JVMs in the super cluster to form an extremely large grid space.
这将允许您使用超级集群中所有JVM的堆空间来形成一个庞大的网格空间。
Here are some additional items to keep in mind when using a secure proxy to route across a super cluster.
在使用安全代理实现跨超级集群路由时，需要考虑下面几个其他事项。
Assuming the use of the familiar HTTP plug-in router, the resulting super cluster topology would look something like Figure 6.
假设使用的是熟悉的HTTP插件路由器，生成的超级集群拓扑结构类似于图6。
The secure proxy can only support routing HTTP protocol for a super cluster.
安全代理只能够支持超级集群的路由HTTP协议。
Many of these steps were detailed in Part 1 and so won't be repeated here, but steps 6 and 7 are specific to a DMZ secure proxy server and its ability to route across a super cluster.
许多步骤已经在第1部分中详述，因此这里不再重复，但是步骤6和7特定于DMZ安全代理服务器及其跨超级集群路由的能力。
应用推荐