Symantec 14541094 Implementation Guide - Page 11

How Symantec Packager works

Page 11 highlights

Introducing Symantec Packager 11 How Symantec Packager works How Symantec Packager works Symantec Packager uses a phased approach for creating custom installation packages. Each phase depends on the output of the previous phase. Figure 1-2 shows the process for creating and deploying packages. Figure 1-2 Overview of Symantec Packager phases Import Products Configure Products Configure Packages Deploy Packages Configure Commands The following process outlines how the Symantec Packager phases build upon one another to let you create custom installation packages: ■ Import product modules into Symantec Packager If the product that you want to customize provides a product module, Symantec Packager automatically imports it. This process extracts the product installation binary files and the product template. The product template details the feature requirements and conflicts, which makes it possible to create custom installations of the product. See "About the Import Products phase" on page 12. To create a custom installation for an unsupported product, you must use a custom command. See "About the Configure Products phase" on page 13. ■ Configure products and commands In the Configure Products phase, you can select the features that you want your users to have and set the default installation options for each product. You also have the option to create custom commands to include in a package. For example, if you want to include a third-party program or batch file in a package, create a custom command for that program. See "About the Configure Products phase" on page 13.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96

11
Introducing Symantec Packager
How Symantec Packager works
How Symantec Packager works
Symantec Packager uses a phased approach for creating custom installation
packages. Each phase depends on the output of the previous phase.
Figure 1-2
shows the process for creating and deploying packages.
Figure 1-2
Overview of Symantec Packager phases
The following process outlines how the Symantec Packager phases build upon
one another to let you create custom installation packages:
Import product modules into Symantec Packager
If the product that you want to customize provides a product module,
Symantec Packager automatically imports it. This process extracts the
product installation binary files and the product template. The product
template details the feature requirements and conflicts, which makes it
possible to create custom installations of the product.
See
“About the Import Products phase”
on page 12.
To create a custom installation for an unsupported product, you must use a
custom command.
See
“About the Configure Products phase”
on page 13.
Configure products and commands
In the Configure Products phase, you can select the features that you want
your users to have and set the default installation options for each product.
You also have the option to create custom commands to include in a
package. For example, if you want to include a third-party program or batch
file in a package, create a custom command for that program.
See
“About the Configure Products phase”
on page 13.
Import
Products
Configure
Products
Configure
Packages
Deploy
Packages
Configure
Commands