Symantec Packager, Implementation Manual

Page: 15 / 98

15 Introducing Symantec Packager
How Symantec Packager works
command and references the locations of any files that you included in the
custom command.
When you build the command configuration file, Symantec Packager creates a
self-extracting executable (.exe) file, which is used in an installation package.
Unlike the command configuration file, the command .exe file does not
reference and is not dependent upon any Symantec Packager files.
Figure 3-5 shows the process for creating custom commands.
Figure 3-5 Configure Products process for custom commands
See “Configuring custom commands” on page 47.
About the Configure Packages phase
During the Configure Packages phase, you select the products and custom
commands that you want to include in an installation package. To do this, you
create package definition (.pkg) files.
If your product supports .msi deployment and you are configuring a single
product installation, package creation is optional. However, a package definition
gives you more options for customizing the installation such as configuring
restart and rollback options and adding custom support information. Symantec
Packager supports deployment of pcAnywhere .msi files only.
On the Configure Packages tab, you create a new package definition file by
selecting from the product configuration files and custom commands that you
customized during the Configure Products phase.
After you select the products and custom commands that you want to include in
the installation package and specify a file name, Symantec Packager saves this
file as a package definition (.pkg) file. The .pkg file, which displays on the
Configure Packages tab, references the .pcg files that it contains.
Product
configuration
(.pcg) file
Lists the
command-line
arguments and
switches
Refers to
optional files
Custom
command build
process
Symantec Packager
displays saved .pcg
file on Configure
Products tab
Symantec Packager
creates .exe file,
which is used in an
installation package