CA Client Automation - 14.0

PDF
English

Virtual Application Image Content and Format

You create a virtual application image from a regular application by using the tools provided by your application virtualization vendor.
CA Client Automation
 supports Microsoft Application Virtualization (Microsoft App-V) and VMware ThinApp. Create the virtual application images with one of these tools before you can use
CA Client Automation
 to package, deploy, and manage virtual applications.
cla140
You create a virtual application image from a regular application by using the tools provided by your application virtualization vendor.
CA Client Automation
 supports Microsoft Application Virtualization (Microsoft App-V) and VMware ThinApp. Create the virtual application images with one of these tools before you can use
CA Client Automation
 to package, deploy, and manage virtual applications.
For information about creating virtual application images, see the vendor documentation for your application virtualization product.
  • Microsoft App-V
    Virtual application image preparation (sequencing) results in few files, including the following files:
    • XML-based Open Software Description files (.osd)
    • Icon files (.ico)
    • A file that stores the complete application code of the virtualized application (.sft)
    • An XML-based manifest file (.xml)
    • A project file (.sprj)
      Ensure that the End User on the target computer does not start the virtual application by double-clicking the .osd file. If the user does so, the communications with the streaming server might not function properly. Start the application by using the desktop shortcut or the Start menu.
  • VMware ThinApp
    Virtual application image preparation (capturing) results in few files and folders, including the following files and folders:
    • A bin folder that contains a single executable file. For program suites, several executable files are required for the user interface. In this case, the bin folder contains a .dat file holding the entire virtual package and small executable files that provide access to the virtual package.
    • A configuration file (.ini)