AutoMate BPA Server supports the import of several file types. These file types can be dependant on where the data originated from. The list of compatible file types are as follows:
AutoMate Package (.AMPKG extension) - The primary file type supported in BPA Server for the purpose of object migration.
AutoMate Markup Language (.AML extension) - The primary file type used in AutoMate version 5 - 8. AML files are also created in BPA when individual tasks are saved directly from the Task Builder by selecting the Save As option.
AutoMate Task Database (.ATL extension) - Used in AutoMate 5 - 8 to store all aspects of a task with the exception of the task steps. This includes managed task properties such as logon, priority and trigger settings.
AutoMate Archive file (.AML extension) - File type used to store backup data designed for use in AutoMate version 6 - 8.
Supported file types can be imported via ”drag and drop” or by use of the Import option located in the Repository or Workflows section of the SMC.
While the steps to import the data contained within the different file types are the same, the behavior of the import process is slightly different depending on what is being imported. Further details about each file type and their import behavior are explained below. Proper instructions to import the supported files into the BPA Server Repository will be explained as well.
An AutoMate Package file contains a .AMPKG extension and is primarily the file type designed in BPA Server for the purpose of object migration. A Package file is created when one or more objects are exported from the Repository of a BPA Server installation. Objects can include workflows, tasks, events, conditions or custom folder structures containing such objects A single AutoMate Package file is capable of storing multiple objects and is not limited to a single object type during export.
When an AutoMate Package file is imported into a BPA Server installation, all objects contained in the file are automatically imported into the corresponding locations in the Repository. For example, if a package contains tasks and conditions, the tasks will automatically import to the Repository’s Tasks folder and conditions will automatically be import to the Conditions folder. Any folder structure contained within the package is recreated in the Repository as well. The folder structure is created relative to the folder currently being displayed when the import begun. If an object with the same name already exists in the same folder path contained within the package, a message dialog will appear prompting whether or not to overwrite the existing object(s).
AutoMate BPA Server supports importation of several kinds of file types from AutoMate 6 - 8 and AutoMate BPA Server. While the steps to import the data contained within the different file types is the same, the behavior of the importation process is a little different depending on what is being imported.
AML (AutoMate Markup Language) is the primary internal language used by AutoMate. AutoMate version 5 - 8. AML files can contain task steps alone (created when the task is saved from the Task Builder) or it can include a ”r;managed” task together with task steps (created when exporting a task from the Task Administrator).
Managed tasks contain additional information about how the task executes in an automated environment, such as priorities, failure handling, logon information and user provided details. A managed task may also include one or more triggers (known as Events or Conditions in BPA Server ). During the import process, BPA Server performs a background conversion of AutoMate 5 through 8 AML files that are imported to the Repository. What occurs during this process varies depending on the contents of the AML file being imported.
The steps contained in the AML file become a new repository task object. The AML file name is used as the name of the new task object.
A new workflow object is created and added to the repository under the Workflows folder. The workflow will contain the new task object and automatically assign it to execute on the default Agent (if a default Agent is selected).
The steps contained in the AML file become a new repository task object. The name of the managed task is used as the name of the new task object.
The properties of the managed task (i.e. priorities, failure handling, logon and user provided details) are transferred to the applicable properties of the new task object.
NOTE: Only those features common between AutoMate 5, Automate 6 and BPA Server are migrated.
If the AML file contains any triggers, they are created as new condition objects and inserted into the Conditions folder in the Repository. The conditions are named based on the name of the managed task. If more than one trigger exists in the AML file, a unique number is appended to the condition name.
A new workflow object is created and added to the Workflows folder of the SMC. If the managed task did not contain any triggers, the workflow will only contain the new task object. If the managed task included triggers, the workflow will contain all the new conditions created from those triggers and automatically link each one to the task object. All objects are automatically set to execute on the default Agent.
If a repository item of the same name already exists, the user will be prompted to ignore the object being imported, rename the object or overwrite the existing repository object.
In this manner, each imported managed task becomes a new, self-contained workflow that will execute the same way in BPA Server as it did in AutoMate.
The AutoMate 5 through 8 Task Database (.atl) file contains managed tasks, properties for each managed task (i.e. details, priorities, logon parameters, and triggers), folder structures created in the AutoMate Task Administrator in which to store managed tasks and references to the task steps contained in the AML file that the managed task executes. However, the steps of each managed task are not stored in an ATL file. Therefore, importing an ATL file into a BPA Server environment is only supported on those machines where an AutoMate installation exists.
This is due to the fact that during the import process of the ATL file, BPA Server will attempt to locate the associated steps contained in the AML file for each managed task on the local machine. If the corresponding AML file cannot be found, the task object will be created, but it will contain no steps.
AutoMate Archive (.ama) files are created by the AutoMate Backup action located in the Task Builder or by the Backup option located in the Task Administrator. These backup files contain all managed task information created by AutoMate 6, such as task steps, properties and triggers. It also includes system preferences, constants and the folder structure of an AutoMate installation.
Unlike migration of an Automate AML file that may contain managed task properties but does not contain information about folder structure, an AMA file is able to fully reproduce the original folder structure of an AutoMate installation during the import process. Therefore, when an AMA file is imported into BPA Server, it can create a folder in each repository location for each managed task folder contained in the AMA file, and places the imported objects into those folders. This is different than a managed task import, which simply places any referenced repository objects into the root of the proper folder.
Compatible file types can be imported to the Repository using the Drag and Drop feature. Instructions to import files via the this method are as follows:
From the Server Management Console, select the Repository section and click the Tasks or Conditions folder or select the Workflows section.
Drag the desired file(s) from its original location and drop them into the Repository or Workflows section of the SMC. Files can be dropped into either the main window or the available folder(s). The imported file is converted into the corresponding BPA Server repository items (depending on the file type). The illustration below demonstrates dragging an AutoMate Package (.ampkg) file into the appropriate locations of the Repository.
Newly imported tasks will subsequently appear in the Repository’s Tasks folder and any associated triggers will merge in the Conditions folder. Additionally, the repository and workflow items and any related folder structure is created from the contents of the imported file.
Instructions to import files using the Import option are entered below:
From the SMC, select the Repository section and click the Tasks or Conditions folder or select the Workflows section.
Click the More button and select Import from the drop-down menu that appears, as shown below, or right-click an empty area in the main viewing area of the Repository or Workflows section and select Import from the pop-up menu.
A window titled Import will appear prompting to select the file type and location of the file(s) to be imported. The default file type is an AutoMate Package (.ampkg) file, however, clicking the drop-down arrow allows selection of other file types as shown below.
NOTE: The proper file type must be selected first in order for the corresponding files to come into view. For example, if the file that is being imported is an AutoMate Markup Language (.aml) file, it will not appear in its original folder location until the matching file type is selected from the proper drop-down list.
Navigate to and highlight the the desired file and click Open to complete the import process.
The imported file is converted into the corresponding BPA Server repository items. Newly imported tasks will subsequently appear in the Repository’s Tasks folder and any associated triggers will merge in the Conditions folder. Additionally, the repository and workflow items and any related folder structure is created from the contents of the imported file.
Exporting Repository Objects