Upgrading from AWCM 4.x to AWCM v6.0 and using Explicit Clustering

Overview

By default, all upgrades to AWCM v6.0, which is bundled with the AirWatch v8.0 installer, will default to using implicit clustering. To configure explicit clustering, you have two options:

  • Perform a fresh installation of AWCM v6.0 (Recommended)
  • Manually configure explicit clustering

 

Performing a Fresh Installation of AWCM v6.0

Perform the appropriate steps below, depending on where your AWCM is installed:

AWCM is Installed on a Standalone Server

1. Perform a backup of the AWCM folder.

2. Uninstall the old version of AirWatch from the Control Panel.

3. Install AirWatch 8.0 (GA or above) and select the AWCM feature.

  • You can now choose Explicit Clustering from the Install Wizard. Follow the instructions listed in the AirWatch 8.0 Installation Guide.

Note: Remember to run the Secure Channel Certificate Installer on the AWCM Server.

4. Restart the AWCM Service.

AWCM is Installed on the Device Services Server

1. Perform a backup of the AWCM folder.

2. Upgrade to AirWatch 8.0 (GA or above).

3. Uninstall the AWCM feature:

a. In Control Panel, select Modify for the AirWatch 8.0 program.

b. De-select the AWCM feature.

c. Run through the Wizard without making any other changes.

4. Re-install the AWCM feature:

a. In Control Panel, select Modify for the AirWatch 8.0 program.

b. Select the AWCM feature.

c. You can now choose Explicit Clustering from the Install Wizard. Follow the instructions listed in the AirWatch 8.0 Installation Guide.

d. Run through the Wizard without making any other changes.

e. Note: Remember to run the Secure Channel Certificate Installer on the AWCM Server.

5. Restart the AWCM Service.

 

Manually Configuring Explicit Clustering

1. Upgrade to AirWatch 8.0 (GA or above).

2. Edit the following parameters in the awcm.properties file:

  • AWCM_HEARTBEAT_INTERVAL_IN_MINUTES: This parameter replaces the AWCM_IDLE_TIMEOUT_IN_MINUTES parameter from the old file.
  • AWCM_CLUSTERING_MODE: Change this value to EXPLICIT (will be IMPLICIT by default).

3. Edit the “hazelcast.xml” file:

  • Under the Network section, list the FQDN for all the AWCM Nodes (including self) that are being custered, along with the port that will be used for communication between them in the following format:
    awcm_cluster.png
  • All AWCM Nodes should be able to reach one another over this port within the Internal LAN.

4. Restart the AWCM Service.

Have more questions? Submit a request

0 Comments

Article is closed for comments.