About Package Definition - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

About Package Definition

Software Manager Reference
6. Make packages available.
Change the package's status to Available to indicate that it is ready for deployment.
See Changing the Package Status
7. Distribute the package group.
Using Group Distribution creates a deployment wrapper .EXE, which contains the
files that will install all packages in the group, the command lines that will run the
installations, and any additional files that will be installed. You can easily deploy the
.EXE with any distribution system (example: Software Management Solution). When
you deploy the .EXE to the destination computers, it installs all the packages and
files and runs all the command lines that are contained in the wrapper.
See Group Distribution
A Wise package definition file defines what is needed to install a package. At a
minimum, this is a command line. However, it can also be the installation file itself,
additional command lines, or any file that needs to be installed. Having a package
definition file lets you use Group Distribution in Software Manager to prepare the
package for deployment.
Defining a package creates a Wise package definition file (.WPF). The package definition
file is saved in its own subdirectory of the share point Projects directory. The files in the
package definition are saved in a Files subdirectory of the package definition's project
directory. This ensures that all the files are in a shared location and are accessible when
the package is distributed.
Defining a Package in Software Manager
A package definition containing at least one command line is required for any package
that you include in a group distribution, except for the following formats: .MSI, .WSI,
.MSP, .MST, .WSE, and .IPF. Those formats have default command lines, and Group
Distribution determines the installation file. However, by defining packages for any of
those formats, you can add additional files to the installation or change the default
command line.
Create a package definition when you need to:
Install a package that you could not otherwise repackage or deploy.
Examples:
A Setup.exe of unknown format and the command line to run it.
A device driver (.INF) with its .CAB files and the command lines to run it.
Add a file or files to a package that is already in the Software Manager database.
Example: When you distribute an .MSI that is in the Software Manager database,
you want to include a script file that sets a registry key after the installation. Create
a package definition for the .MSI, which specifies the script file and a command line
to run it.
Change a command line for a package that is already in the Software Manager
database.
You can also change the command lines for a package on the Group Properties and
Group Distribution dialog boxes.
on page 108.
on page 130.
Preparing Packages for Deployment
114