Install Bot Agent on your local device and connect it to Control Room. In order to run bots on that local device, ensure that you add it to the list of enabled host devices.

Starting with Automation 360 v.29, we have enhanced the Bot Agent installer by including new .exe files for the Bot launcher, Node manager, Triggers, and Child session launchers. The following changes occur in the installer when you:
  • Install the Bot Agent, java.exe will be replaced by NodeManager.exe.
  • Run a bot, javaw.exe will be replaced by BotLauncher.exe.
  • Configure a trigger, the trigger will be activated with TriggerListener.exe instead of javaw.exe.
  • Run a bot with Automation Co-Pilot (integrations), javaw.exe will be replaced with ChildSessionLauncher.exe.
Note: When you install or update the Bot Agent, you must include the new .exe files in the trusted list.
Note: Before installing the Bot Agent on a device, ensure that you turn off or disable the Automatically detect settings option in the Proxy settings window of that device.

Prerequisites

  • To install the Bot Agent, the Windows installer policy must be enabled for your local device.
  • The read, write, and execute permissions must be enabled for the Bot Agent folders on your local device.
  • Ensure that the local device system date and time are in sync with the current date and time so that the device registration is successful.
  • Ensure that the following conditions are met:
    • The available storage (free disk space) meets the minimum hardware requirements.

      For more information, see Bot Agent device requirements.

    • You have write permission to the global cache directory where the bot files are downloaded by default.
    • You have the required permission to other folders if the bot logic is trying to write or update data on the local device

Credential requirements

The Bot Agent version available for download is the latest and compatible with the Control Room version that is used.

Note:
  • You can now install the Bot Agent on a device with an existing Enterprise 11 client. However, ensure that the Automation 360 and Bot Agent versions that you are using are v.25 or later.
    • A Bot Creator can log in and access both Automation 360 and Enterprise 11 client to create bots.
    • Attended Bot Runners can run bots from both Automation 360 and Enterprise 11 Control Room instances.
    • Unattended Bot Runners can deploy bots by using the run and schedule permission on the same device.
  • You cannot run bots from Enterprise 11 and Automation 360 at the same time.
  • You cannot install a Bot Agent on a device with an existing Enterprise 10 client.
  • When the Bot Agent is installed on a device where Enterprise 11 client is also installed and then you uninstall the client, you might face login issues with the device. Therefore, you must uninstall and re-install the Bot Agent on the device.
Note: If the Bot Agent is installed at system level, then as part of the configuration update, permissions for the Global Cache folder is set as follows:
  • Full access for System user and Administrator group.
  • Read, Execute, and List access for Authenticated users.

Procedure

  1. Use a supported browser to log into Control Room through your Automation Anywhere URL.
  2. Install the Bot Agent and add a local device by choosing one of the following options:
    • From the menu on the left, click the device icon to connect a local device.
    • Go to the Devices page, and click the Connect local device icon located at the top-right of the Devices list.
  3. Click Connect to my computer.
    The Bot Agent setup file is downloaded.
  4. Follow the steps outlined in the wizard.
    Authenticated proxy access: If your device's access to the internet is controlled through an authenticating proxy server, you are prompted to provide the proxy server authentication details. These credentials are required for the device to communicate with the Control Room.

    To enable the authenticated proxy, register the device through a Google Chrome browser with the Automation 360 Chrome extension enabled.

    Note: The Chrome and Edge extensions are installed for Google Chrome and Microsoft Edge Enterprise browser users respectively, even if the device is offline. The extension is downloaded with the Bot Agent MSI installer file.
  5. Select an option to install the Bot Agent either at the system level or user level.
    • To install at the system level, select All users/System level (Recommended)

      All users of the device can use this Bot Agent. However, users installing the Bot Agent must have administrator privileges.

      When you install Bot Agent at the system level, you can configure custom proxy. For more information, see Configure custom proxy during Bot Agent installation.

    • To install at the user level, select Only for me (enggadmin).

      The Bot Agent will be available only to the individual user.

  6. Enter the following in the Additional information screen:
    • Device nickname (optional)
    • Device type (single user or multiple user)
      Note: For a multiple user device, enter the number of concurrent sessions that will be allowed. A minimum of two concurrent sessions is supported.
  7. Click Done.
    • The Bot Agent is installed to the default location C:\Program Files\Automation Anywhere\Bot Agent.
    • The Bot Agent is registered as a Windows service: Automation Anywhere Bot Agent Service.
    • A shortcut to access Automation Co-Pilot Desktop Assistant is added to the Windows Start menu and desktop.
    • The Java Runtime Environment (JRE) files are installed with the Bot Agent in the Bot Agent install folder: C:\Program Files\Automation Anywhere\Bot Agent\jre.
  8. Set the user device credentials so that your device can run bots.
  9. Refresh the Devices page and verify that the local device is added.
    You can identify the devices by their IP address and hostname.
    Note: After you remove a device, wait for 35 seconds to re-register the device.

Troubleshooting:

  • If you face any issues registering your device, see Automation 360: Error while registering device - An unexpected problem occurred (A-People login required).
  • If the Bot Agent service is paused and does not start after installation, see Automation 360 Error: Device is disconnected or needs upgrade (A-People login required).
  • If you are using Google Chrome browser version 94 or later and if you face issues registering your device in a Control Room On-Premises, we recommend that you configure the Control Room for HTTPS instead of HTTP. Alternatively, use Microsoft Internet Explorer or Mozilla Firefox to register your device.

    If you face any issues adding a new device, see Unable to Add New Device (A-people login required).

  • We recommend that you do not remove the Google Chrome extension. If you remove the extension, existing Google Chrome policy will restrict you from adding the extension (online or offline) even after you reinstall the Bot Agent. However, if you have removed the extension, use the following instruction to add it:
    • Go to the Google Chrome extension store to add the extension online. See Automation 360 extension for Chrome.
    • Drag the ChromeExtension.crx file (C:\Program Files\Automation Anywhere\Bot Agent\AABrowserAgent) to the Google Chrome extension tab (three vertical dots menu on top-right > Settings > Extensions).
  • Similarity, ensure that you do not remove the Microsoft Edge extension as the existing Microsoft Edge policy will restrict you from adding the extension (online or offline) even after you reinstall the Bot Agent. For Microsoft Edge extension store, see Microsoft Edge extension for Automation 360

Watch the following video on how to install the Bot Agent in Automation 360:

Next steps

Optionally, Edit profile.

If your device is set with a proxy, see the tasks that apply to your proxy settings, Connect Bot Agent to a device with a proxy.