Importing Objects

You can reuse objects from another Galaxy in your Galaxy. This saves you a lot of 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.

You can import objects 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.

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, you can choose how you want naming and version conflicts handled.

You should perform an "Upload Runtime Changes" before importing a new version base template if instances of the template are deployed. This saves changes made at Runtime to the Galaxy database.

Objects that were created in Application Server 2014 R2 or later cannot be imported into a Galaxy running an older version. For example, you cannot import an object created in Application Server 2017 into a Galaxy running Application Server 2012.

Note: The Application Server version is not the same as the Codebase version. Objects with newer Codebases can be imported.

To import objects

1. On the ribbon, select Galaxy, then select click Import.

2. Select Objects, then select Objects from package. The Importing objects dialog box appears.

3. Browse for the file with either an .aaPKG or an .aaPDF extension. You can select more than one file. Click Open. The Import Preferences dialog box appears.

   

4. In the Objects with same Tagname and Codebase as an existing object area, select one of the following:

   • Skip: Do not import leaves the existing object unchanged.

   • Overwrite objects if the imported configuration version is higher replaces the existing object with the object being imported if the imported object has a newer configuration. This is the default.

   • Overwrite objects regardless of configuration version replaces the existing object regardless of whether the existing object has an older configuration or the same configuration.

5. In the Base Templates with a different revision number in the Codebase or a different minor version area, select one of the following:

   • Skip: Do not migrate - objects with an older codebase are not migrated when a newer codebase exists in the Galaxy.

   • Migrate - objects with an older codebase are migrated when a newer the replacement object.

     For more information about migrating, see After You Import.

6. In the Objects with same Tagname but with a different Codebase area, select one of the following:

   • Skip: Do not import leaves the existing object unchanged.

   • Rename object in Galaxy imports an object with a matching tagname but a different codebase from the existing one. The existing object is not overwritten but is renamed.

   • Rename importing object imports an object with a matching tagname but a different codebase from the existing one. The existing object is not overwritten. The imported object is renamed.

7. In the Template Protection Change Management area, select the checkbox to prohibit overwriting an unprotected object with a protected object (default). Clear the checkbox to allow overwrites.

8. Click Import. The import process starts.

9. When the import process is complete, you can start using the objects you imported.