Migrating tasks from AutoMate 5 or AutoMate 6 to BPA Server 7 is a simple and straightforward procedure that can be executed in different ways. A user can perform the migration of an individual task, a group of tasks, or all the tasks at the same time. A user can also include the triggers attached to those tasks during migration. Any of these options can be utilized when importing tasks to BPA 7. BPA 7's AML (AutoMate Markup Language) implementation is backward compatible so that tasks created in AM 5 or AM 6 will run without any modifications or complications in BPA 7. Additionally, BPA 7 is designed to run side-by-side with previous versions allowing task migration to be quick and effortless. This article will discuss the different methods to properly import legacy tasks from a previous version of AutoMate to BPA Server 7.
EXPORTING FROM A PREVIOUS VERSION
In order to include any triggers associated with the task(s) during migration, it is required that the task be initially exported. To properly export a task from the AM5 or AM6 Task Administrator, highlight the task(s) you wish to export and select ‘File’ -> ‘Export’ or right click the mouse on the highlighted task(s) and select ‘Export’ from the right-click properties. You will then be prompted to choose a location to save each task. Simply select a location and click ‘Save’ to complete the process. You will need to click ‘Save’ for each task being exported. The newly exported tasks along with their triggers (if there are triggers attached to those tasks) will then be saved in AML format to the location selected. You can then simply import those AML files to BPA 7 (import procedures are explained below under “IMPORTING TO BPA SERVER7”).
NOTE: If the tasks that you wish to migrate do not include triggers or if you decide not to include attached triggers during migration, you can skip the export process and simply point to the AML files located in your default managed task location during import.
TASK DATABASE FILE OPTION
Another option to migrate from a previous version to BPA 7 is to import the entire task database file. This is ideal if you wish to import all of your legacy tasks as well as their triggers. A task that is created, edited, or executed in AM5 or AM6, and all the managed task properties including trigger information, are written to a task database file. If using AM6, this file is named AM6Taskfile.atl and is located in C:\DocumentsandSettings\AllUsers\ApplicationData\NetworkAutomation\AutoMate6. In Windows Vista, it is located in C:\ProgramData\NetworkAutomation\AutoMate6. If using AM5, the file is named AM5Taskfile.atl and is located in C:\DocumentsandSettings\AllUsers\ApplicationData\NetworkAutomation\AMTA. Since the ATL file is a vital component of AM5 and AM6, it is recommended that you create a backup of this file before you import any tasks to BPA 7.
NOTE: If BPA 7 is installed on a separate machine, it may be necessary to copy the task files (.AML files) or task database file (.ATL file) to the machine where BPA 7 resides before importing them.
IMPORTING TO BPA SERVER 7
In order to import your task files (.AML files) or task database file (.ATL file) to BPA Server 7, start the Server Management Console (SMC), select the ‘Repository’ view, then highlight the ‘Tasks’ folder. Select ‘More’ -> ‘Import’ or right click the mouse anywhere inside the ‘Tasks’ folder to select ‘Import’ from the right-click properties. An ‘Import’ window will then appear prompting you to choose the file type and location of the file(s) you wish to import. Select *.aml or *.atl as the file type. Then navigate to and highlight the proper file(s) that you wish to import and click ‘Open’ to complete the process. Alternately, you can properly import the AML file(s) by simply dragging and dropping them into the ‘Tasks’ folder. The newly imported tasks will subsequently appear in BPA 7’s ‘Tasks’ folder and any associated triggers will merge in the ‘Conditions’ folder.
NOTE: When selecting files from the ‘Import’ window, the proper file type must be selected first in order for the corresponding files to come into view.