Many people hesitate to upgrade because they assume that installing Automate 6 on a system with Automate 4 will interfere or convert their existing Automate tasks; this is not the case. Because so many of our users relied on Automate 4 for mission-critical tasks, Automate 6 was designed from the very beginning to operate side-by-side with Automate 4 and/or 5. This design eliminates time pressure and risk normally present when upgrading mission critical software, allowing the user to migrate when it is convenient even piece by piece, if desired. The following article outlines the simple process of upgrading to Automate 6 on a workstation with an existing installation of Automate 4
Locate the existing computer running Automate 4 and install Automate 6 just as a new user would. You will note that Automate 6 installs to a different folder by default.
The Automate 4 default installation folder is:
The Automate 6 default installation folder is:
It is recommended that you do not install to the same folder as your existing Automate 4 installation.
When you have finished the Automate 6 installation, reboot the system. Rebooting is not always required but is recommended to make sure everything starts okay for unattended operation. If the install requests that you reboot the system, rebooting is required for correct operation. After the reboot, both versions of Automate should be running in the system tray. Tasks will still be present in Automate 4 and will run when they are triggered. Opening the Automate 6 Task Administrator (known as the Configuration Manager in Automate 4) will show that the only tasks present in that system are the samples which are included. Automate 6 cannot be used to administer the tasks in Automate 4 or vice-versa. Since the two systems run totally independent of each other, the Automate 4 Configuration Manager should be used to administer Automate 4 tasks and the Automate 6 Task Administrator should be used to administer Automate 6 tasks.
To assist users in converting existing Automate 4 tasks to Automate 6's new AML (Automation Markup Language) format (first introduced in version 5), Network Automation has made a Migration Utility. Using the Migration Utility is straightforward and is completely non-destructive to your existing Automate 4 installation. Upon downloading and running, the Migration Utility will perform a read-only scan of the existing Automate 4 task database and ask which Automate 4 tasks should be converted. Select the tasks to be migrated (usually "All" since the process is read-only and will not affect existing tasks).
Note that there is no need to export Automate 4 tasks first as the migration utility reads the internal task database of the Automate 4 installation directly.
Upon completion of the migration, a file with a .AML extension will be created for each task that was migrated. When ready, these file may be imported in to Automate 6 by opening the Task Administrator and selecting from the menu: File | Import. Once imported, the task can be tested in Automate 6 - if confirmed to be operating correctly, it may then be disabled in Automate 4 via the Automate 4 Configuration Manager. Repeat this process for all tasks being moved to Automate 6. This does not need to be done all at one time, since the tasks are still functional in Automate 4 the migration process can be done task by task at your leisure. Once all Automate 4 tasks have been migrated, tested and disabled in Automate 4, there is no longer a need for the Automate 4 so it can be uninstalled.
No Need To Export Automate 4 Tasks
Because there seems to be so much confusion about this issue, it bears repeating that there is no need to export tasks from Automate 4 before performing the migration. The migration utility reads the task database in Automate 4 and creates files that can be imported into Automate 6.
Migrating To A New Machine
If migrating tasks from an old Automate 4 computer to a new computer which will be running Automate 6, simply run the migration utility on the Automate 4 system and copy the AML files that are created to the new Automate 6 system. Import the AML files into Automate 6.
Automate 4 scripts utilizing pure BASIC can still be used in Automate 6 and will be converted, however the following Automate 4 specific objects cannot be used in Automate 6
In most cases there are other ways of accomplishing the same functionality as was provided by these objects, usually using Actions included in the "visual" portion of the AML language (non-BASIC). Nonetheless, adapting your tasks will take more time if any of these objects were relied upon heavily.
This advanced information is not relevant to the migration process itself, however it may be interesting to those wondering how Automate 6 task storage works compared to previous versions. Furthermore, it is not necessary to understand task storage concepts to use Automate 6 as the interface masks the underlying storage system.
Automate 6 stores tasks in a completely different manner than previous versions of Automate. In Automate 4 all tasks and triggers were stored in a proprietary database which was located in the Automate 4 program folder. Automate 6 stores triggers and other task properties in the Automate Task Library file (by default: C:\Documents and Settings\All Users\Application Data\Network Automation\Automate 6\AM6Taskfile.atl), this file contains pointers to the actual task steps, which reside in individual text files with the extension .AML [Automation Markup Language] (by default stored in: C:\Documents and Settings\All Users\Documents\My Automate Tasks).
The task storage architecture was changed to be in compliance with Microsoft Windows document creation and storage guidelines and is also much better suited to task sharing, re-usability and manual editing of Automate tasks.
Applies To: Automate 4, Automate 5, Automate 6
Still have questions? We can help. Submit a case to Technical Support.