Each task includes important details such as 'Trigger', 'Security,' 'Priority' and 'Logon' settings which are located in the 'Managed Task Properties' window. Normally, you can access the task properties from the Task Administrator by double-clicking a task or right-clicking a task and selecting "Properties."
Whether migrating tasks from a previous version or moving tasks from one Automate server to another, the proper method to accomplish this would be to use the 'Export' and 'Import' features located in the File menu of the Task Administrator. Simply copying tasks from one default managed task location to another will not migrate triggers and other task properties. Furthermore, importing externally saved task files (without initially exporting them) will cause the triggers and managed task properties to be lost.
Migrating tasks from a previous version
Upgrading from Automate 5 to Automate 6 is a simple process. Automate 6's AML (Automation Markup Language) implementation is backward compatible so that tasks created in Automate 5 will run without modification in Automate 6. Automate 6 is designed to run side-by-side with Automate 5 allowing migration at your own pace. When all tasks are tested and moved from Automate 5, it can be uninstalled and the upgrade to Automate 6 is complete.
Moving tasks from one Automate to another
If moving tasks from an Automate installation on one machine to an Automate residing on another machine, in order to preserve the triggers and managed task properties, simply export the files from the Automate residing on the first machine and then import them into the Automate residing on the second machine.
All triggers, and applicable task properties (excluding task steps) are saved to an automate task database file named AM6Taskfile.atl which resides in C:\Documents and Settings\All Users\Application Data\Network Automation\Automate 6. In Automate 5, the file is named AM5Taskfile.atl and is located in C:\Documents and Settings\All Users\Application Data\Network Automation\AMTA.
If migrating tasks to the same version (i.e. Automate6 located in workstation #1 to Automate 6 located in workstation #2), the following instructions will provide another method in which to save task triggers and properties:
Applies To: Automate 5, Automate 6
Still have questions? We can help. Submit a case to Technical Support.