Unclustering from Essentials

Analytics 1.4.x introduces a streamlined method for collecting data from resources, making it possible to monitor Essentials instances without having to be clustered with them. To simplify existing installations, and to reduce the consumption of resources on monitored servers, Geocortex Analytics 1.4.x will not support configurations where Analytics is in a multi-server cluster with Geocortex Essentials.

The result of these changes means that:

You uncluster from Essentials by running the Unclustering Utility. You must run the utility on the Analytics Hub server first. Running the utility uncouples Analytics from the existing Essentials cluster and creates a new cluster that includes only Analytics components.

When you create a new cluster, the name of the cluster must be unique and not used by an existing cluster.

You must also run the Uncluster Utility on all the machines that were part of the former cluster so that all the Analytics agents can then be connected to the new cluster and all the Essentials instances are fully disconnected from the Analytics Hub machine.

Because the Geocortex Core service must be shut down while you are unclustering Agent machines, you should not upgrade or uncluster when Essentials is at peak usage but preferably during a maintenance window.
(Geocortex Core Service must be running on all the machines in the cluster when you uncluster the Hub server.)

Unclustering Scenarios

How and whether you uncluster depends on your current deployment and configuration of Analytics and Essentials. Below are some examples of when you must, or when you should not uncluster.

Analytics and Essentials are on the same server

Unclustering is not possible when Analytics and Essentials are on the same machine.

If you want to separate Analytics from Essentials, you can uninstall Essentials and install it to a different machine, however the process is best done with the help of Latitude Geographics Support.

If your configuration includes a cluster with multiple Essentials instances, and Analytics is installed on one of them, then upgrading will put you into a configuration that is not supported. In this case, you should move Essentials to a new server.

Multiple servers with Analytics and Essentials on different machines

You must uncluster the Analytics Hub from all your clustered servers after you upgrade to 1.4. x. Run the Unclustering Tool on the Analytics Hub server and then on all the other servers that were in the old cluster, even if they did not have an Analytics agent installed.

You have to upgrade to 1.4.x before you uncluster.
When you are unclustering the Hub server, the Core Service must be running on all the Agents in the cluster because when the Hub server is unclustered, it retrieves Analytics data from the other nodes in the cluster and it cannot do so if they are not available.
When you are unclustering Agent machines and you have three or more nodes in your cluster, you must ensure the Core Service on all your Agent machines in the cluster are off when you run the Uncluster Utility on any of the agent machines.

Leave Core running on the Hub that you just unclustered.

The Uncluster Utility turns the Core Service back on at the end of the process, so right after you have unclustered each Agent, you will need to turn that Core Service off again to ensure the Core Service remains off when you uncluster the next agent machine.

Essentials is clustered with Analytics to provide a third node for load balancing

You will need to find a new third node to cluster Essentials with. You may want to wait to upgrade Analytics to 1.4.x until you a have a third node in place.

Analytics Version is lower than 1.1.

  1. Upgrade the Analytics Hub to 1.3.x.

    You can only upgrade to version 1.4.x from versions 1.3.x.
    If you are upgrading to 1.3.x and have previously not clustered with Essentials, then do not cluster during the upgrade as you will have to uncluster again when you upgrade to 1.4.
  2. Upgrade the Analytics Hub to 1.4.

  3. If your Analytics is clustered with one or more machines with Essentials installed, run the Uncluster Utility on the Hub server and create a new cluster, noting the name and secret of the new cluster.

  4. If Analytics was monitoring any Essentials instances, uninstall all Essentials Components for Analytics installations on these machines.

  5. Upgrade to Analytics 1.4.x on all the agent machines.

    For more information about upgrading and detailed step-by-step instructions, see Geocortex Analytics Upgrading

    When you are unclustering the Hub server, the Core Service must be running on all the Agents in the cluster because when the Hub server is unclustered, it retrieves Analytics data from the other nodes in the cluster and it cannot do so if they are not available.
    When you are unclustering Agent machines and you have three or more nodes in your cluster, you must ensure the Core Service on all your agent machines in the cluster are off when you run the Uncluster Utility on any of the agent machines.

    Leave Core running on the Hub that you just unclustered.

    The Uncluster Utility turns the Core Service back on, so right after you have unclustered each Agent, you will need to turn that Core Service off again to ensure the Core Service remains off when you uncluster the next agent machine.
  6. If you have any Essentials nodes in the cluster, run the Uncluster Utility on each node/server that has Essentials installed on it.

  7. If you have a cluster of three or more nodes, once you have run the Uncluster Utility on all the Agent machines, restart the Core Service on all the Agents.

Uncluster the Analytics Hub Server

It is important that you run the Uncluster Utility on the Analytics Hub server before you run it on all the other servers in the cluster.

When you are unclustering the Hub server, the Core Service must be running on all the Agents in the cluster because when the Hub server is unclustered, it retrieves Analytics data from the other nodes in the cluster and it cannot do so if they are not available.

You can run the Uncluster Utility independently or as part to the Analytics 1.4.x upgrade when the final window gives you the option to run the Uncluster Utility.

The procedure below details the steps to run the Uncluster Utility from the file system.

To uncluster the Hub server:

  1. On the Hub server, in Windows Explorer, navigate to the folder where the Uncluster Utility is stored.

    The default installed location for the utility is:

    C:\Program Files\Latitude Geographics\Geocortex Analytics\Uncluster Utility\UnclusterUtility.exe

  2. Double-click the Uncluster Utility.exe to run it.

    The Uncluster Utility opens.

  3. In the New Cluster Name box, type in the name of the new cluster.

    This must be a unique name.

  4. In the New Cluster Secret box, type in the secret you want to use for the new cluster.

    Be sure to make a note of the secret for this cluster.

  5. Click Uncluster.

    A progress bar appears at the bottom of the window to indicate what is happening and where in the process the utility has reached.

    When the unclustering is complete, the utility displays the following message:

    If the unclustering process fails, the utility will try to roll back the server to its previous state. If you get an error message, follow the directions in the error message. If the error is unrecoverable, then please contact Latitude Support.

Uncluster from all Agent Servers in the Cluster

You must uncluster from all the servers that were in the previous cluster even if they did not have an Analytics Agent installed. There are several possible scenarios for servers that would have been in the cluster:

If you are unclustering Agent machines and you have a cluster with three or more nodes, you must ensure the Core Service is not running on all agent servers but is running on the Hub server while you run the Uncluster Utility.

As the Uncluster Utility turns the Core Service on again at the end of its process, this means that on agent machines, you have to stop the Core Service on each machine both before you run the Uncluster Utility and again after you run the Uncluster Utility.

Do not turn off the Core Service on the Hub Server that you just unclustered.

The process to run the Uncluster Utility is the same for each of the above scenarios, but the wording in some of the text boxes changes depending on the applications found on the server.

To uncluster other servers:

If you have a cluster with three or more nodes, stop the Core Service on all the Agent machines in your cluster before you run the Uncluster Utility on any one Agent machine. Do not stop the Core Service on the Hub server.
  1. On an agent server, in Windows Explorer, navigate to the folder where the Uncluster Utility is stored.

    The default installed location for the utility is:

    C:\Program Files\Latitude Geographics\Geocortex Analytics\Uncluster Utility\UnclusterUtility.exe

    The Uncluster Utility is packaged with Analytics 1.4. If only Essentials is installed on the machine, the utility won't be on that machine. You can copy the utility from an Analytics machine or download it from the Support Center.
  2. Double-click the Uncluster Utility.exe to run it.

    The Uncluster Utility opens.

    The wording in the yellow box may change depending on whether or not there is an Analytics agent or Essentials instance installed on the server.
  3. In the New Cluster Name box, select the name of the new cluster that you entered on the Hub server.

    When you select the new cluster, the Document Store URI populates automatically to point to the Hub server.
    If the URI cannot be found, or the incorrect URI appears, you can enter the URI manually.

  4. In the New Cluster Secret box, type in the secret of the new cluster.

  5. Click Uncluster.

    A progress bar appears at the bottom of the window to indicate what is happening and where in the process the utility has reached. The steps may differ depending on which resources are on this machine, for example, Essentials only, Essentials with an Agent etc.

    When the unclustering is complete, the utility displays the following message:

    If the unclustering process fails, the utility will try to roll back the server to its previous state, but this is not guaranteed. If you get an error message, follow the directions in the error message. If the error is unrecoverable, then please contact Latitude Support.

    The following steps apply only if you have three or more nodes in your cluster and you are unclustering Agent machines:

    1. Stop the Core Service again on this machine before you run the Uncluster Utility on the next machine.
    2. When you have unclustered all the Agent servers, restart the Core Service on all the servers.

© 2018 Latitude Geographics Group Ltd. All Rights Reserved.

Documentation Version 1.4