Symantec 14541094 Implementation Guide - Page 47

Configuring custom commands, About configuring custom commands

Page 47 highlights

6 Chapter Configuring custom commands This chapter includes the following topics: ■ About configuring custom commands ■ Working with custom commands ■ Configuring custom commands ■ Building and testing custom commands About configuring custom commands Symantec Packager lets you create custom commands to include in your packages. Examples of custom commands include installations of unsupported products, batch files, third-party executables, command-line arguments, or simple file copies. Custom commands let you simplify application deployment by including multiple tasks in one package. Once defined, you can reuse custom commands in different packages. When you create a custom command, Symantec Packager creates a command configuration file. A command configuration file is a generic product configuration file that does not reference a product template file. Therefore, custom commands do not depend on the Import Products phase. The build process for custom commands creates a self-extracting executable (.exe) file, which can be tested before including it in a package.

  • 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

Chapter
6
Configuring custom
commands
This chapter includes the following topics:
About configuring custom commands
Working with custom commands
Configuring custom commands
Building and testing custom commands
About configuring custom commands
Symantec Packager lets you create custom commands to include in your
packages. Examples of custom commands include installations of unsupported
products, batch files, third-party executables, command-line arguments, or
simple file copies. Custom commands let you simplify application deployment
by including multiple tasks in one package. Once defined, you can reuse custom
commands in different packages.
When you create a custom command, Symantec Packager creates a command
configuration file. A command configuration file is a generic product
configuration file that does not reference a product template file. Therefore,
custom commands do not depend on the Import Products phase. The build
process for custom commands creates a self-extracting executable (.exe) file,
which can be tested before including it in a package.