Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
88 views10 pages

Migration POC

The document provides steps for migrating bots from Enterprise 11 or Enterprise 10 to Automation 360. It discusses how the bot scanner analyzes bots and provides a report on which bots can be migrated. The bot scanner will provide a migration factor to indicate if a user is ready to migrate or should wait. It then outlines the specific steps to download and use the bot scanner tool to migrate bots, including selecting source and destination folders, running migration, and verifying migrated bots are functional in Automation 360.

Uploaded by

sankar naidu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
88 views10 pages

Migration POC

The document provides steps for migrating bots from Enterprise 11 or Enterprise 10 to Automation 360. It discusses how the bot scanner analyzes bots and provides a report on which bots can be migrated. The bot scanner will provide a migration factor to indicate if a user is ready to migrate or should wait. It then outlines the specific steps to download and use the bot scanner tool to migrate bots, including selecting source and destination folders, running migration, and verifying migrated bots are functional in Automation 360.

Uploaded by

sankar naidu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Migration:

The migration process copies all your Enterprise 11 or Enterprise 10 entities such as users, roles,
lockers, and bots to Automation 360.

All the Enterprise 11 or Enterprise 10 entities are ready for use in Automation 360 after they are
successfully migrated, except bots and MetaBots.

Bots are copied as .atmx files and MetaBots are copied as .mbot files. You must convert these bots
and MetaBots to the Automation 360 format before you use them.

Bot scanner phase-----------


Analyze the bot and provides the report and summarize no of bots commands and variables that are
ready for the migration or not.

Provide the recommendation whether you are ready for migration or not.

If migration factor is above 90% then it will tell you to proceed with migration else it will ask you to
wait for the migration.

Steps to migrate from V11 to A360:


 Login to apeople website and click on recent version of Automation Anywhere 360 Build.
 Go to installation setup for downloading bot scanner.

 Click on AAE Bot Scanner A360 zip file.


 Click on download option for bot scanner in local device.

 Once it is unzipped, double click on Automation_360_Bot_Scanner application and click on


continue.
 The repository path that contains all the V11 version different files.

 Now select the repository path where .atmx and .mbot files are present and destination
folder and click on create report.
 The bot scanner analyses the A11 version files. Once completed, open a report.

 The bot scanner report shows the possibility of migration as shown in the picture below.
 It will also show if any actions are needed, Review required, no review required and Non
Migratable details.
 Download the csv file to know the status of the all migrated bots at a time.

 Check the commands which can be migrated to A360 from the Commands tab.
 Download the csv file to know more about the commands at a time.

 Check the local folders for migration summary and bots.


 Check the reports in the destination folder.

 Create a bot and migrate the files by bot migration command and click the run button.
 The bot will run successfully and create a bot in Automation A360.

 Navigate to the newly generated migrated bot.


 Open the bot and go through the code line by line and understand it properly.

 If we have any errors, Then rectify those errors as per requirement and run again.

Finally the bot migrated successfully from V11 to A360.

You might also like