The software delivery software packaging process for virtual applications (through the Virtual Application Package Registration Wizard) creates three software packages for the first packaging of a virtual application:
This package installs and executes the virtual application locally on the target computer. The Standalone package contains procedures and, for Microsoft App-V, configuration files. It also contains a dependency to the Staging package, which holds the virtual application image. Therefore, the Staging package is installed on the target computer before the Standalone package is installed.
This package creates all shortcuts and file associations (as created by the original installation). The Standalone package does not contain the application bulk data. The bulk data is stored in the Staging package and installed on the target computer as a dependency to the Standalone package.
This package is named using the following format:
application name–vendor tool abbreviation–SA
Example: DeveloperStudio–AV–SA (Microsoft App-V) or DeveloperStudio–TA–SA (VMware ThinApp)
This package consists of procedures, tools, and configuration files. It creates shortcuts and file associations on the target computer. The shortcuts on the target computer allow the launch of the application from the scalability server, which acts as the streaming server. The virtual application image is not part of the Streaming package, which implies that the application image is not staged on the target computer. Instead, the application image needs to be staged on the scalability server. The administrator must verify that the Staging package is installed on the scalability server first in order for the Streaming package to work.
Note: The Streaming package is not created when a virtual application is imported as an update to an existing virtual application package. The Streaming package does not need to be updated because the included shortcuts are already pointing to the Staging package (which is updated).
This package is named using the following format:
application name–vendor tool abbreviation–SM
Example: DeveloperStudio–AV–SM (Microsoft App-V) or DeveloperStudio–TA–SM (VMware ThinApp)
This package provides access to the virtual application for both standalone and streaming modes of package delivery. The Staging package contains the bulk data, that is, the virtual application image. For standalone delivery, the image is staged locally on the target computer. For streaming delivery, contents from the image are streamed to the target computer. As specific parts of the application are requested by the user, those parts are streamed to the target computer from the scalability server (which acts as the streaming server).
Note: The Staging package is installed automatically (as a dependent package) when you install a Standalone package on a target computer. However, if you uninstall a Standalone package, the corresponding Staging package is not uninstalled automatically. You need to schedule an uninstall job to remove the Staging package.
This package is named using the following format:
application name–vendor tool abbreviation–SG
Example: DeveloperStudio–AV–SG (Microsoft App-V) or DeveloperStudio–TA–SG (VMware ThinApp)
Updates to Virtual Applications
When packaging virtual application updates, the software delivery packaging process creates two software packages only: Standalone and Staging. The Streaming package is not created, since this package includes just the client links to the Staging package and the virtual application. These links are not affected by application updates. The Standalone and Staging packages for updates are registered with a version number that is higher than the original packages.
Update packages have the same name that was used for the former packages, with a higher version number. While the version number is not part of the package name (it is stored internally), it is displayed as a suffix to the package name when shown in the DSM Explorer, Software Delivery Library.
Downgrades to Virtual Applications
You can also downgrade a virtual application package. A downgrade is similar to an update. You need to create the virtual application image (which includes the application) with the target version for the downgrade. The packaging of a downgrade is similar to the packaging of an update. The Standalone and Staging packages only are created. The downgraded packages have the same name that was used for the former packages, with a higher version number (similar to update packages).
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|