CA Client Automation - 14.0

PDF
English

How Virtual Application Packaging Works

Contents
cla140
Contents
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 already be available before you use the Wizard to create the software delivery package. The image must be accessible from the computer where CA ITCM is running. This 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. Images must be available on or accessible to the computer running CA ITCM.
  2. The administrator browses the virtual application image. This step allows the administrator to verify that the selected image is a valid virtual application image. The Wizard analyzes the virtual image and extracts the information needed to create the Software Delivery packages.
    The package name is based on the virtual application name and is limited to 20 characters (for example,
    my_productname_is_20
    -TA-SG). If there is a duplicate product name, the administrator must modify the current package name to create the package.
  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.
    For more information on 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 stating that the package names are not unique. 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. The descriptions of Virtual Application Discovery and Inventory provide more information about creating definitions for 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.
Virtual Application Packages
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:
  • Standalone
    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)
  • Streaming
    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.
    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)
  • Staging
    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).
    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).
Create a Virtual Application Software Package
The Virtual Application Package Registration Wizard lets you create a virtual application package and import it into the Software Package Library.
To create a virtual application software package
  1. Verify that a virtual application image has been created for the application you want to package. The image should be located on or accessible from the same computer where CA ITCM is running.
  2. Navigate to the Software Package Library folder in DSM Explorer where you want to create the package.
  3. Right-click the folder and select Import, Virtual Application Package.
    The Virtual Application Package Registration Wizard opens.
  4. Proceed through the Wizard pages selecting the virtual application image.
    The Wizard creates three virtual application packages: Standalone, Streaming, and Staging. The packages are placed under the Software Package Library folder where you launched the Wizard.
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.
    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.
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).
Virtual Application Infrastructure Package Templates
CA ITCM lets you create virtual application software packages from Microsoft Application Virtualization (Microsoft App-V) images or VMware ThinApp images. However, before you can deploy and run these virtual application packages, you must install specific vendor infrastructure software on the servers and target computers where you want to deploy the virtual applications. The infrastructure software contains vendor tools and modules that allow the virtual application to be installed and run.
For more information on vendor infrastructure software requirements, see the descriptions of Preparing a Target Computer for Deployment of a Microsoft App-V Virtual Application and Preparing a Target Computer for Deployment of a VMware ThinApp Virtual Application.
You can use CA-provided templates to create vendor infrastructure software packages. The following templates are available for your use:
  • Microsoft App-V Virtualization Desktop Client (App-V Client for standard desktops)
  • Microsoft App-V Virtual Client for Remote Desktop Services (App-V Client for Terminal Servers)
  • Microsoft App-V Server
  • VMware ThinApp
You need to insert the appropriate vendor software modules into these templates. The packages you create with the templates are standard software delivery software packages. You can register the infrastructure software packages in the Software Package Library.
The file structure in the infrastructure package template is the same as the structure found in a standard Software Delivery software package - a root folder, the “reginfo” folder, and additional folders and/or files.
  • reginfo subfolder
    The templates contain all information needed to register the package in the Software Package Library and link it to other dependent infrastructure packages.
  • Additional folders and files
    The templates include installation modules for the software packages. For infrastructure packages, you must copy these modules from the vendor’s installation media.
The template assists you with identifying the installation modules that you need to copy into its subfolders. In each template, there is an image file that lists the vendor files that are required. For example, the template for Microsoft App-V Desktop Client includes a “client_files.JPG” file. This file indicates that three files are needed:
  • AppVirtReadme.htm
  • Setup.exe
  • Setup.msi
The infrastructure package templates are provided for your convenience. However, you may choose to install the vendor infrastructure software on your own. If you do so, ensure that the software is installed on all servers and target computers where you want to deploy virtual applications and that required permission keys are set in the registry.
In addition to the infrastructure package templates, the CA ITCM DVD kit includes the following package: Microsoft Application Error Reporting 11.0.6558.0. You can deploy this error reporting package with the client and server packages. For more information about this package, see the Microsoft product documentation.
Create Infrastructure Software Packages for Microsoft App-V
You can create Microsoft App-V infrastructure software packages using CA-provided templates. The packages you create with the templates are standard software delivery packages.
This procedure assumes that you have the following products available: Microsoft System Center Application Virtualization Streaming Server, Microsoft Application Virtualization Desktop Client, and Microsoft Application Virtualization Client for Remote Desktop Services. The following procedure describes how to create packages for the server and both types of clients.
To create infrastructure software packages for Microsoft App-V
  1. Access the following folder on the CA ITCM installation media: 
    examples\AV_Templates\Microsoft AppV packages
  2. Copy the Microsoft AppV packages folder (and the entire tree structure below it) to your local machine (for example, to D:\AppV-Packages).
  3. Open the image file “server_files.JPG” in the 1.vol subfolder and view the Microsoft product files that are required: 
    Microsoft AppV packages\Infrastructure Package for AppV Server\1.vol
  4. Copy the required files (as shown in “server_files.JPG”) from the Microsoft System Center Application Virtualization Streaming Server installation media to the following subfolder: 
    Microsoft AppV packages\Infrastructure Package for AppV Server\1.vol
  5. Remove the file “server_files.JPG” from the following subfolder: 
    Microsoft AppV packages\Infrastructure Package for AppV Server\1.vol
  6. Open the image file “client_files.JPG” in the Desktop Client template and view the Microsoft product files that are required: 
    Microsoft AppV packages\Microsoft Application Virtualization Desktop Client
  7. Copy the required files (as shown in “client_files.JPG”) from the Microsoft Application Virtualization Desktop Client installation media to the template: 
    Microsoft AppV packages\Microsoft Application Virtualization Desktop Client
  8. Remove the file “client_files.JPG” from the Desktop Client template: 
    Microsoft AppV packages\Microsoft Application Virtualization Desktop Client
  9. Open the image file “client_files.JPG” in the Desktop Client for Remote Desktop Services template and view the Microsoft product files that are required: 
    Microsoft AppV packages\Microsoft Application Virtualization Desktop Client for Remote Desktop Services
  10. Copy the required files (as shown in “client_files.JPG”) from the Microsoft Application Virtualization Desktop Client for Remote Desktop Services installation media to the template: 
    Microsoft AppV packages\Microsoft Application Virtualization Desktop Client for Remote Desktop Services
  11. Remove the file “client_files.JPG” from the Desktop Client for Remote Desktop Services template: 
    Microsoft AppV packages\Microsoft Application Virtualization Desktop Client for Remote Desktop Services
  12. Copy the required files (as shown in “files.JPG”) from the Microsoft Application Error Reporting installation media to the template: 
    Microsoft AppV packages\Microsoft Application Error Reporting
  13. Remove the file “files.JPG” from the Application Error Reporting template: 
    Microsoft AppV packages\Microsoft Application Error Reporting\1.vol
  14. Open the image file “files.JPG” in the Application Error Reporting template and view the Microsoft product files that are required: 
    Microsoft AppV packages\Microsoft Application Error Reporting\1.vol
  15. Select all folders under the AppV packages folder (for example, D:\AppV-Packages) in Windows Explorer and drag and drop them into the Software Package Library in the EGC GUI.
    Microsoft App-V infrastructure software packages are created and registered in the Software Package Library. You need to deploy the following packages on target computers.
    • The infrastructure package for the server is named using the following format: 
      Infrastructure Package for AppV Server
    • The infrastructure package for the standard desktop computer is named using the following format: 
      Infrastructure Package for AppV Client
    • The infrastructure package for the terminal server is named using the following format: 
      Infrastructure Package for AppV Client for Remote Desktop Services
Create Infrastructure Software Packages for VMware ThinApp
You can create VMware ThinApp infrastructure software packages using CA-provided templates. The packages you create with the templates are standard software delivery software packages.
This procedure assumes that you have already installed the following product: VMware ThinApp.
To create infrastructure software packages for VMware ThinApp
  1. Access the following folder on the CA ITCM installation media: 
    examples\AV_Templates\VMWare ThinApp packages\Infrastructure Package for ThinApp Client
  2. Copy the Infrastructure Package for ThinApp Client folder to your local machine.
    The location on your local machine must be accessible to the Virtual Application Package Registration Wizard.
  3. Open the image file “vmware_file.JPG” from the following subfolder and view the VMware product file that is required: 
    Infrastructure Package for ThinApp Client\1.vol
  4. Copy the Thinreg.exe executable file from the VMware ThinApp installation media to the following subfolder: 
    Infrastructure Package for ThinApp Client\1.vol
  5. Remove the file “vmware_file.JPG” from the following subfolder: 
    Infrastructure Package for ThinApp Client\1.vol
  6. Select the Infrastructure Package for ThinApp Client folder in Windows Explorer and drag and drop it into the Software Package Library in the EGC GUI.
  7. The infrastructure packages are named using the following format: 
    Infrastructure Package for ThinApp Client
    The VMware ThinApp infrastructure software package is now registered as a standard software delivery package in the Software Package Library.