BACK

Migration Pre-Planning: How to Use Bot Scanner Utility

Migration Pre-Planning: How to use the Bot Scanner Utility

Bot scanner utility scans your TaskBots and MetaBots (built on V11/V10) and provides you a report with the list of Bots that can and cannot be currently migrated from V11.x or V10.x to Automation 360. It also provides you the specific details about missing variables or commands due to which a particular bot cannot be migrated (at this point in time) along with an estimated future build when this particular functionality is expected to be available for planning your migration.

With every Automation 360 release, a new version of the Bot scanner utility is released and you can re-run the utility on your existing TaskBots and MetaBots to check the latest status of migration readiness.

Pre-Requisites for Bot Scanner Utility

Windows machine running the Bot Scanner Utility will need a minimum of 2 GB RAM and access to the Bots to be analyzed.

Steps to download Bot Scanner Utility and Analyze the bots

Navigate to the Bot Scanner Utility from this link. (A-people login required).

Click on Automation Anywhere Enterprise A2019.xx (xx is the Latest_Build_number) link.

Click on Installation Setup

Select AAE Bot Scanner zip file, and then click Download.

Extract the files from the downloaded zip folder.

Double click on the file AAE_Bot_Scanner.exe to launch the utility

Bot Scanner Utility launches as shown below:

Before we enter the details into the Bot Scanner Utility, we need to take a copy of the Task bots and MetaBots from the 11.x Production CR and store in a different folder and name it as ‘Automation Anywhere’. For ex: C:\temp\Automation Anywhere

Enter the folder path where your TaskBots and MetaBots are placed, the folder path where you would like the output report to be placed, and Select the timeout (in minutes). Any bot taking more time than this would be skipped from scanning. Click ‘Create Report’.

Once the scanning is completed, Click ‘Open report’.

You will see a summary report as shown below.

Now, let’s understand each of the sections in this dashboard.

As a rule of thumb, if more than 90% of the bots can be migrated successfully, you will see a message ‘Proceed with migration’ highlighted in Green at the top left corner. It will also show the percentage of bots that are ready to be migrated and the work required to migrate the remaining bots. This section also consists of links to the additional reading material from AAU and Docs portal. It provides a link that consists of the list of all the unsupported features for migration for the latest release.

Let’s move on to the table as shown below.

In this report, it is showing that 151 bots are scanned in total and 150 bots can be migrated, and the remaining 1% cannot be migrated for now. The number 151 does not correspond to the sum of Task bots and MetaBots, as each logic in a MetaBot is considered to be a separate bot for the purpose of migration.

Now, let’s discuss about the details table as shown below.

On the left side panel, you can filter by the Bots and Commands which correspond to the bots that can and cannot be migrated.

Let’s choose the section ‘Bots that can be migrated’ now.

It again consists of 2 sections: Review Required and No Review Required. Even though these bots are ready for migration, Automation Anywhere recommends some of the bots to be reviewed to ensure we are satisfied with the way it is migrated, test them for expected functionality before they are moved to Production. The table consists of the bot name, the path for that particular bot, and the number of times a particular bot is used as a child bot within other bots. You can download this list in CSV format by clicking on the button ‘Download .csv’.

In our example, the report says that 7 bots need to be reviewed. However, we would like to know the specific issues which needs to review. To see the details, click ‘Messages’.

Now we can see the list of issues and the number of bots each issue affects in the table.

We can see the commands used in the bots and the number of times these commands have been used in the bots by clicking on ‘Commands’ as shown below.

Next is to know about the bots and commands which cannot be migrated. Click on the section ‘Bots that can’t be migrated now’.

Here we can see the bots and commands which are not yet supported for migration. It also gives an indication about the estimated release with which this command will be available for migration. But kindly note that this is an estimated release only and subject to change.

You can also view the XML reports for each of the Task bots and MetaBots validated for migration readiness by navigating to the output folder added in the Bot scanner utility screen.

You will see a folder called ‘raw-data’ which contains the XML files which feeds data to the HTML summary report which we already reviewed. This folder consists of 3 sub-folders MetaBots, Migratable_Bots and Non_Migratable_Bots which has the details about each of the commands used in the bots and how these are interpreted during the migration.

You can read through each of the XML files to know more about each command used in the bot.

This concludes the tutorial, hope you learned about how to use the Bot scanner utility.

Conclusion:

Bot scanner utility is the first step in the migration process, to know about the migration readiness for your bots and gives you a fair understanding about whether to proceed with migration or if you still have to wait for the upcoming releases and then start your migration process.

To learn about the next steps to migrate your 11.x/10.x bots, please visit the prepare section in this link.