Using Software Delivery › Using the Software Package Library › Registering Virtual Applications › How Virtual Application Packaging Works › Create a Virtual Application Software Package Update

Create a Virtual Application Software Package Update

The Virtual Application Package Registration Wizard lets you create a virtual application package update and import it into the Software Package Library.

To create a virtual application software package update

1. Verify that an updated virtual application image has been created for the update application you want to package. The image should be located on or accessible from the same computer where CA ITCM is running.

   Note: For Microsoft App-V, you must create the updated virtual application image using the Active Upgrade method of the App-V sequencer. For more information about the Active Upgrade method, see the Microsoft App-V product documentation. You can also access the Microsoft web site (http://www.microsoft.com) and search the Microsoft TechNet information for the "Methods for Upgrading or Updating Virtualized Applications" article.

2. Navigate to the Software Package Library folder in DSM Explorer where you want to create the package update.
3. Right-click the folder and select Import, Virtual Application Package.

   The Virtual Application Package Registration Wizard opens.

4. Proceed through the Wizard pages and select the updated virtual application.

   The Wizard asks you to select the Staging package for your updated virtual application.

5. Select the former Staging package (latest version) that was created for the original virtual application.

   The Wizard creates two virtual application packages: Standalone and Staging. The packages are placed under the Software Package Library folder where you launched the Wizard.

Note: 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).