Topic 8.1.1: Exporting and Importing Objects
- Exporting Automation Objects
- Use the ArchestrA IDE’s export function to share objects with other users or to recreate them in other Galaxies. The resulting file (.aaPKG extension) contains the selected objects, their associated templates and the configuration state of those objects. The export file can later be imported into the same or another Galaxy.
- If any of the selected objects are currently checked out, only the checked in versions are exported. Exporting an entire Galaxy is similar to using the Galaxy Database Manager utility to back up the database. However the change logs for the objects are not exported while they are saved during backup. Also, the backup process retains security model settings for objects while exporting them does not.
- When exporting an object instance, it will also include the parents of that object all the way back to and including the base template.
- To export an object
- Select an object in the Template Toolbox or Application Views pane.
- From the Galaxy menu, select Export/AutomationObject(s).
Note: You can export more than one object with this function by first multi-selecting objects (Shift+Click or Ctrl+Click). If you want to export all of the objects in the Galaxy, point to Export and then click All AutomationObjects.
- The Export Automation Object(s) dialog box appears.
- In the Export Automation Object(s) dialog box, browse to the path and filename (.aaPKG extension) of the export file and click Save. Click Cancel to terminate the export function. If you click Save, a progress box is displayed.
- When the export process is finished, click Close. The resulting .aaPKG file can be used to import the chosen objects into another existing Galaxy.
- Exporting All
Automation Objects
- The Exporting All Automation Objects function is much
like the Exporting Automation Objects procedure. The key difference being that
with the Export Automation Objects function only the objects that are selected
are exported into a .aaPKG file. With the Export All Automation Objects
function all of the objects and any derived templates are also exported.
Importing Automation
Objects
- Objects can be reused from another Galaxy in your
Galaxy. This saves time if the objects are already set up in another Galaxy.
- Importing instances previously exported from a Galaxy retains previous associations, when possible, such as assignment, containment, derivation, and area.
- Objects can be imported from exported .aaPKG files or from an .aaPDF file. An .aaPDF file contains the configuration data and implementation code for one or more base templates. It is created by a developer using the ArchestrA Object Toolkit.
- Before starting, you cannot have two objects with the
same name or more than one copy of the same version of an object in the same
Galaxy. When you import an object, these conflicts are identified and you can
manage them.
- To import Automation objects
- On the Galaxy
menu, select Import/Object(s).
Importing Automation Objects
- On the Galaxy menu, select Import/Object(s).
- The Import AutomationObject(s) dialog box appears.
- Browse for the file with either a .aaPKG or a .aaPDF extension. You can select more than one file. Click Open.
- The Import Preferences dialog box appears.
- In the Objects from same toolkit and vendor area, select one of the
following:
- Skip objects with same conflict or newer codebase leaves the existing object unchanged.
- Overwrite objects with name conflicts if their configuration version is higher replaces the existing object with the object being imported if the codebases are the same and the imported object has been edited more often than the existing object.
- Migrate objects with a newer codebase also overwrites existing objects if the codebases (versions) are the same. In addition, this option will migrate the state of existing objects to the newly imported version if the object supports it. For more information about migrating, see the Application Server Installation Guide.
- In the Objects from different toolkits and/or vendor but with same tagname area, select one of the following:
- Skip does not import the object when a name match exists in the Galaxy.
- Rename Object in Galaxy renames the existing object by appending to its current name the string (up to four characters) you type in the Append to Object Name box. The default value is _old but you can change it to any four- character string.
- Rename Importing Object renames the object being imported by appending to its current name the string (up to four characters) you type in the Append to Object Name box. The default value is _new, but you can change it to any four-character string.
- Click OK to start the import process.
- When the import process is complete, you can start using the objects you imported.
Last modified: Friday, 10 April 2020, 4:03 PM