Importing a Virtual Software Package File
Software Manager Reference
Package Import
on page 34
Revision Control
on page 80
Wise Task Manager in the Wise Package Studio Help
You can import a single virtual software package (.WVP or .VSA) into the Software
Manager database from a network or local drive. One reason to import virtual software
packages is for purposes of impact and risk assessment.
See
Impact and Risk Assessment
A .VSA file is a virtual software archive file. A .WVP file is a virtual software project file
that compiles to a .VSA file.
See Integration with Software Virtualization Solution in the Wise Package Studio Help.
When you import a .VSA file into Software Manager, it is converted to a .WVP file.
Because of this, only .WVP files are actually imported into the Software Manager
database. However, when you import a .VSA file, it is copied to the share point, and
when you distribute a .WVP file, its compiled .VSA file is distributed.
Importing a .VSA or .WVP file requires the Software Virtualization Agent to be installed
on your computer.
Note
If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise
Connector to import the virtual software package from the Software Manager database
into Software Management Framework. You can then use Software Management
Solution to distribute it.
To import a virtual software package file
1.
(Enterprise Management Server only.) If multiple databases are open, select a
database in the Applications/Packages pane.
2.
Select Packages menu > Import.
The Import Type page appears.
3.
Mark Import a single file into the Software Manager database.
4.
In File, specify a .WVP or .VSA to import. Be sure to select the appropriate file type
from the Files of type drop-down list on the Open dialog box.
5.
The following item becomes enabled:
Distribute source files to the share point directory
Mark this to copy all source files to a single, centralized location.
Clear this check box to import the package description into the Software
Manager database without copying its source files to the share point directory.
This prevents other users from exporting the package, unless source files are
stored on a shared network drive.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the
same application and package names. If you clear this check box and the
application and package names are already in the database, the new package is
not imported.
on page 125.
Importing Packages
59
Need help?
Do you have a question about the SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 and is the answer not in the manual?