14 total views
In this section, we are sharing our experience on Code Migration from Automation Anywhere version 11 where code includes MetaBots into Automation 360. We are sharing important points on Code Migration Interview Questions and Answers. This will help you with clear interview-based Automation 360 interview questions.
You can also visit our YouTube Channel EasyWay2Learn to see our training videos. Based on RPA Realtime Projects for Automation Anywhere, UiPath, and IQ Bot.
Explain the steps for Migrating MetaBots Code into Automation 360.
In Order to migrate Automation Anywhere MetaBot Code into Automation 360. You need to follow the below steps:
(a) You must have Automation Anywhere atmx file and MetaBot mbot files.
(b) Remove extra or unused lines of code, Assets or Logics which is not required before migration.
(c) Test your code in Version 11 and fix bugs if any present before migrating to Automation 360.
(d) Use BOT Scanner tool to see the % of code changes required once migration is completed.
Go to Automation 360 and look for Package “Bot Migration”. Select “Migrate Legacy Bot” from the list. Select your task BOT or MetaBot which you are migrating. You will get 3 options to choose your atmx and mbot files.
1. Control Room File :
Select atmx or mbot files if it is available in Control Room (e.g. D:\taskbot.atmx or D:\metabot.mbot)
2. Desktop File :
Select atmx or mbot files if it is available in ShareDrive or in your local drive (e.g. D:\taskbot.atmx or D:\metabot.mbot)
3. Variable :
Under this you can pass the path and extension of your file, which you are going to migrate. (e.g. D:\taskbot.atmx or D:\metabot.mbot)
Output Folder Path: Here you can give the output location where xml file will create once migration completed successfully for taskbot or metabot.
Migration time out in mins: Here in this box, you can timeout in minutes which will stop the migration after given timelines.
Migration process will take some time based on number of lines or assets or logics available in taskbot or metabot.
Once BOT run completed successfully it will create of copy of Task BOT with same file name available with atmx. It will create separate folder for MetaBot file where all the logics will be there.
Click Here To Download Automation Anywhere Code with MetaBot and Try to Migrate in Automation 360 Platform.
What are the code changes needs to be done after migration to Automation 360?
Once code Migration completed successfully in Automation 360 it will looks like as attached image.
You need to re-map the MetaBot logic and make the necessary changes in the code base on error details like map variables, check loop and other commands where you have got error after migration to Automation 360.
You need to execute the BOT to identify if any error found after code migration. If is there any error you need to analyze and fix the issue first.
Click Here to see our other Post on Robotic Process Automation