Configuring for dual IP servers

If your Control Room server has multiple IP address or network interface cards (NICs), you can manually update the cluster.properties file to include the Primary IP address.

Prerequisites

Complete Control Room installation.

Note:

As of Automation Anywhere Enterprise Version 11.3.4, this configuration is completed during installation. Skip this post-installation task.

Note: Updating the cluster.properties file requires complete downtime, this means all the Automation Anywhere Enterprise clients are disconnected and schedule triggers do not run.

Update the cluster.properties file to ensure the caching service requirement to define a single IP address for the primary NIC of the Control Room.

Ensure that you complete these tasks on all the Control Room nodes in a high availability cluster.

Procedure

  1. Locate the cluster.properties file in your Enterprise Control Room directory.

    For example, default location is:

    C:\Program Files\Automation Anywhere\Enterprise\config\

    If the file does not exist in your Control Room directory, create the file.

  2. Add the following property options to the cluster.properties file.

    Add ignite.local.static.ip=<primary_ip_address>. For example:

    ignite.local.static.ip=172.16.20.168

    Note: The ignite.local.static.ip property is configured with a single IP address of the primary NIC of the Control Room, with which the communication between the Control Room nodes is expected.
  3. Save the cluster.properties file.
  4. Restart the listed services in the following order:
    1. Automation Anywhere Control Room Caching
    2. Automation Anywhere Control Room Messaging
    3. Automation Anywhere Control Room Service
  5. To ensure all the cache are in sync, restart the rest of the Automation Anywhere Enterprise Windows services.
    For a full list of services, see Enterprise 11: Verifying Automation Anywhere Windows services.