Symantec 14541094 Administration Guide - Page 41

Building a product configuration file, Building a package, Build, Close

Page 41 highlights

Creating custom installation packages 41 Building product installations and packages Building a product configuration file Building a product configuration file lets you create an .msi file that you can use for testing or installation. Symantec Packager supports MSI installation for pcAnywhere product modules only. You do not need to build a product configuration file to include it in a package. Symantec Packager stores the .msi files in the Symantec Packager data directory. You can view these files on the Deploy Packages tab if you edit the Symantec Packager preferences to list supported .msi files. You can use an industry-standard, third-party deployment tool to deploy the pcAnywhere .msi file. The Symantec Packager Deployment Tool does not support deployment of .msi files. To build a product configuration file 1 In the Symantec Packager window, on the Configure Products tab, select the product configuration file that you want to build. 2 On the File menu, click Build. The Product Build Status window appears, which provides information about the progress of the build and logs any problems that have occurred. If the product build is successful, the last line in the Product Build Status window reads as follows: Product was built successfully. 3 In the Product Build Status dialog box, click Close. Building a package During the build process, Symantec Packager retrieves information from the package definition file and product configuration files to determine what products to include in the installation file, as well as the product features, installation instructions, and custom settings. Symantec Packager then checks the contents of the package for product conflicts. If Symantec Packager encounters a product conflict, the build process stops. You must resolve the conflict, and then repeat the build process. After checking for product conflicts, Symantec Packager verifies that product requirements are met. This includes verification that all required products are included in the package definition file. If Symantec Packager encounters an error, the user receives an error message; however, the build process continues. After completing the validation phases, Symantec Packager creates a self-extracting executable file and places it on the Deploy Packages tab for testing and distribution to licensed users.

  • 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
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109

Building a product configuration file
Building a product configuration file lets you create an .msi file that you can use
for testing or installation. Symantec Packager supports MSI installation for
pcAnywhere product modules only. You do not need to build a product
configuration file to include it in a package.
Symantec Packager stores the .msi files in the Symantec Packager data directory.
You can view these files on the Deploy Packages tab if you edit the Symantec
Packager preferences to list supported .msi files.
You can use an industry-standard, third-party deployment tool to deploy the
pcAnywhere .msi file. The Symantec Packager Deployment Tool does not support
deployment of .msi files.
To build a product configuration file
1
In the Symantec Packager window, on the Configure Products tab, select the
product configuration file that you want to build.
2
On the File menu, click
Build
.
The Product Build Status window appears, which provides information about
the progress of the build and logs any problems that have occurred. If the
product build is successful, the last line in the Product Build Status window
reads as follows:
Product was built successfully.
3
In the Product Build Status dialog box, click
Close
.
Building a package
During the build process, Symantec Packager retrieves information from the
package definition file and product configuration files to determine what products
to include in the installation file, as well as the product features, installation
instructions, and custom settings. Symantec Packager then checks the contents
of the package for product conflicts. If Symantec Packager encounters a product
conflict, the build process stops. You must resolve the conflict, and then repeat
the build process.
After checking for product conflicts, Symantec Packager verifies that product
requirements are met. This includes verification that all required products are
included in the package definition file. If Symantec Packager encounters an error,
the user receives an error message; however, the build process continues.
After completing the validation phases, Symantec Packager creates a
self-extracting executable file and places it on the Deploy Packages tab for testing
and distribution to licensed users.
41
Creating custom installation packages
Building product installations and packages