Understanding the Behavior of Imported Application Packages

After an import, packages are automatically associated with their application inventory item as they were related in the source App Volumes Manager.

If the application does not exist while importing, App Volumes Manager creates an application by using the application properties and then associates the package to the new application inventory item.

After an import, applications and packages are listed in the Inventory tab of the App Volumes Manager admin UI.

Note: Imported packages follow the behavior described in this section only when they have been created or updated by App Volumes Manager 4, version 2012 or later. Any packages created before App Volumes Manager 4, version 2012, have a different import behavior even when imported to a later version. For optimal import functionality, ensure all App Volumes Manager servers are upgraded to App Volumes Manager 4, version 2012 before performing import actions. For information about upgrade, see App Volumes 4 Installation Guide.

App Volumes Manager performs the following functions to ensure that the package gets associated to the correct application:

• Any update to the package properties such as package description or package stage is applied to all storage locations of the package.

  Such an update ensures that when a package is imported, the package remains associated to the correct application.

• Any update to the application properties such as application name and description is applied to all packages of the application including to all package locations within the same App Volumes Manager instance.
• If the same package is copied to multiple storage locations, on an import, the source App Volumes Manager instance detects the package including all its duplicates and imports them to the target App Volumes Manager instance.
• Application owner information is applied to the package on import.

Note: App Volumes Manager does not import an application's assignments and the assignment type, Marker.

If an application package is marked as CURRENT, though the package is imported, the package does not have the CURRENT marker after the import.