Software Delivery › Tasks › Register/Import Virtual Application Software Packages › How Virtual Application Packaging Works

How Virtual Application Packaging Works

You can create a standard software delivery package from a virtual application image by using the Virtual Application Package Registration Wizard. The virtual application image must be accessible from the computer where Client Automation is running. The Wizard also allows you to create update packages for virtual applications that were previously converted to software delivery packages.

The process to create and import virtual application packages uses the following general steps:

1. The administrator opens the Virtual Application Package Registration Wizard and locates a virtual application image.
2. The administrator browses the virtual application image and verifies that the selected image is a valid virtual application image.
3. (Optional) If the virtual application image represents an update to a virtual application, the administrator identifies the Staging package that was originally created for the virtual application.
4. The administrator reviews the summary of the virtual application package just created and finishes the Wizard.
5. The Virtual Application Package Registration Wizard creates three software packages for each virtual application image:

   Standalone

   This package is used to install and execute the virtual application locally on the target computer.

   Streaming

   This package is used to downstream the virtual application from a streaming server and execute it on the local computer.

   Staging

   This package provides access to the virtual application for both standalone and streaming modes of package delivery. This package contains the virtual application image.

   Note: For more information about the types of virtual application packages, see the description in the Virtual Application Packages section.

6. The Wizard begins the process of importing the virtual application packages into the Software Delivery Library by determining if the package names are already listed in the library.
   1. If the package names are already in the library, an error message appears and the packages are not imported.
   2. If the package names are not already in the library, the Wizard imports the three packages: Staging, Standalone, and Streaming.
   3. If the packages are update packages, they are imported and registered with higher version numbers. Two packages only are created for updates: Staging and Standalone.
7. The administrator creates the definitions for the new virtual application packages.

After a virtual application package is included in the Software Delivery Library, the administrator can then deploy it and manage it using standard software delivery methods.

Note: For more information about virtual application packaging, see the Software Delivery Administration Guide.