Scan Enterprise 11 or 10 bots using Bot Scanner
Before you migrate to Automation 360, it is important to verify the migration readiness of your bots. Scan the bots using Bot Scanner and analyze the generated report for information about the commands and variables used in these bots and how many of these commands and variables are supported for migration.
Ensure you meet the system requirements for using the Bot Scanner:
- Hardware requirements
Processor 2.66 GHz or higher (64-bit) RAM 2 GB or higher Disc space 200 MB
- Software requirements
Operating systems: Windows 7 or later (32-bit and 64-bit)
You can also use the Bot Scanner to scan and identify bots that use Internet Explorer that can be converted to a supported browser.
Download the latest version of Bot Scanner from the Automation Anywhere Support site.
- Navigate to the A-People Downloads page (Login required).
Click the Automation 360 v.xx
The xx in the link refers to the release number. For example, Automation 360 v.21.
- Click the Installation Setup folder.
- Click the AAE Bot Scanner zip file, and then click Download on the toolbar.
Extract the files from the zip file you have downloaded and double-click
Note: Ensure that you save the AAE_Bot_Scanner.exe file in a location path that does not contain a double-byte character. Otherwise, the Bot Scanner encounters an error when it is run.
You can use the Bot Scanner to scan bots that use Internet Explorer. The scanner generates a report that provides details on the number of bots that can be converted and the number of bots that cannot be converted to a supported browser.
From the Automation Anywhere Bot Scanner
dialog box, select one of the following options:
The second and third options provide Internet Explorer usage statistics that helps you to convert Internet Explorer bots to a supported browser.
- Migration to Automation 360
- Migration + Bots using Internet Explorer
- Bots using Internet Explorer
In the Automation Anywhere Bot Scanner dialog box, enter
the location of the folder that contains the bots that you want
to analyze in the Select repository path field.
Important: You must create a copy of the Control Room repository and provide the location of the copied folder instead of the actual repository folder.
Copy the Control Room repository.
For example, if the current location of the repository is C:\ProgramData\AutomationAnywhere\Server Files\Default\Automation Anywhere, you must copy the Automation Anywhere folder.
Paste the copied repository at a temporary location. For example,
D:\My Bots folder.
You must provide this location (D:\My Bots) in the Select repository path field in Step 3.
- Copy the Control Room repository.
Enter the location where you want to save the generated report
in the Select destination folder field.
Note: The Bot Scanner related files and folders in the destination folder are overwritten if you have specified the same location when you have used the Bot Scanner previously.
Enter a value in the Timeout field to specify
the maximum time the Bot Scanner should take to analyze
If the scanning of a bot takes more than the value specified in the Timeout field, Bot Scanner stops scanning that bot and proceeds to scanning other bots in the repository.
Click Create report.
The Bot Scanner starts analyzing the bots available in the repository.
The Bot Scanner displays an error if it scans a bot that is created using an unsupported version of Enterprise Client. You must upgrade the bot to a supported version of Enterprise Client and scan the bot again.
You can click Stop scanning when the Bot Scanner is analyzing the bots to cancel the
The summary report and individual reports are available for the bots that were analyzed before the operation was canceled.
- Click Open report to open the summary report in the default browser after the Bot Scanner has completed analyzing all the bots available in the repository.