Controlled cluster

SuperMap iServer supports child nodes to join the cluster in a controlled manner, which is applicable to the case of the free child node. The child node does not need to provide services but can receive the control of the parent node. Once the child node opens the controlled cluster, it is subject to the full control of the parent node, and its own existing service instances and iServer WebManager are disabled while the service instances and data of the parent node will be synchronized to the child node. In which, the service instance corresponding to the service component cluster and the spatial processing will be filtered to the child node.

The child node as the cluster member in the controlled mode, is only be used to process the request forwarded by the parent node.

As shown in the figure above, both the controlled child node (ID2) and non-controlled child node (ID3) can exist simultaneously in a cluster system. The configuration method that the child node joins the cluster in the controlled way is as follows:

• Open the system configuration file of the child node (ID2)([SuperMap iServer installation directory]\webapps\iserver\WEB-INF\iserver-system.xml), enable and modify <controllable>, then restart the child node service. For more information, please see Managing the cluster with the configuration file.
• If the parent node (ID1) opens security control, the non-local child node needs to click "Permit" on the configuration cluster page of the child node. If the parent node doesn't open the security control, then it doesn't need any operations.

After the child node opens the controlled cluster, the parent node will automatically synchronize services and data to the child node, so the parent node can forward the request of the client to the child node for processing.