About Virtual Software Packages - Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference

Hide thumbs Also See for WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0:
Table of Contents

Advertisement

About Virtual Software Packages

Wise Package Studio Reference
Not available in Standard Edition.
Creation of virtual software packages
In Wise Package Studio, you can use the following tools to create a virtual software
package:
Software Manager
Software Manager lets you enable packages that are in the Wise Software
Repository for the Software Virtualization Solution (SVS). You can enable .MSI
packages or any type of package that has an associated package definition file.
When an SVS enabled package is installed on a target computer where the Software
Virtualization Agent is present, the enabled package can create a virtual software
layer, install the package into the layer, and save and activate the layer. If the
Software Virtualization Agent is not present, the package is installed normally. An
SVS enabled package retains any configuration logic of the installation. (Example: If
the original installation contains a prerequisite that checks for a specific version of
the .NET Framework runtime and installs it if needed, this is retained in the enabled
package.)
See About SVS Enabled Packages in the Software Manager Help.
SetupCapture
SetupCapture lets you convert an existing .EXE or .MSI installation into a virtual
software package. You can run SetupCapture from within Virtual Package Editor or
as a stand-alone tool to capture the installation. You can then edit the package with
Virtual Package Editor. A virtual software package created with SetupCapture does
not retain any of the installation's configuration logic.
See About SetupCapture in the Virtual Package Editor Help.
Virtual Package Editor
Virtual Package Editor lets you edit any virtual software package. You can edit the
contents of a layer, exclude data from a layer, and add deletion entries or data
layers. You can also add command lines or WiseScripts to be executed when a
layer's events are triggered.
See About Virtual Package Editor in the Virtual Package Editor Help.
Virtual Package Editor also lets you create a new package as a virtual software
layer. You can create an application layer or a data layer. When you create a layer,
the output for that layer can be a virtual software layer or virtual software project
file (.WVP). When you compile a .WVP file, it generates a .VSA file.
See
Wise Package Studio File Types
Distribution and management of virtual software packages
After you create a virtual software package, you can use Package Distribution to
distribute it to a network directory or an FTP server. You also can import virtual software
packages (.WVP and .VSA) into Software Manager for purposes of impact and risk
assessment.
Because there is no need to detect conflicts between a virtual software package and
other packages, ConflictManager does not generate conflicts for these packages. By
default, virtual software packages do not appear in ConflictManager, but you can change
the conflict filtering options to display them.
Introduction to Wise Package Studio
on page 31.
30

Advertisement

Table of Contents
loading

This manual is also suitable for:

Wise package studio 8.0

Table of Contents