Symantec 14541094 Implementation Guide - Page 44

Building and testing custom products, Building custom products

Page 44 highlights

44 Configuring custom products Building and testing custom products 3 Do one of the following: ■ Click OK to save your changes and close the Product Editor dialog box. ■ Click Apply to save your changes and continue configuring the product configuration. 4 If prompted, type a file name, and then click Save. Building and testing custom products You can build and test your custom product before you include it in an installation package. Symantec Packager stores testable Microsoft Software Installer (.msi) files in the folder that is specified for the Deploy Packages tab in Symantec Packager Preferences. Building custom products During the build process, Symantec Packager retrieves information from the product configuration file to determine which files to include in the custom product, as well as the command-line parameters, installation options, and custom settings. Symantec Packager then checks the contents of the custom product for conflicts and errors. If Symantec Packager encounters a conflict, the build process stops. You must resolve the conflict and repeat the build process. After you complete the validation process, Symantec Packager creates a Microsoft Software Installer (.msi) file, which you can use for testing purposes. Symantec Packager places the .msi file in the folder that is specified for the Deploy Packages tab. This folder is usually located in the following directory: \Documents and Settings\\My Documents\Packager\Deployment Symantec Packager supports installation of pcAnywhere .msi files only. You can view these files on the Deploy Packages tab if you edit the Symantec Packager preferences to list supported .msi files. To build custom products 1 In the Symantec Packager window, on the Configure Products tab, select the custom product that you want to build. 2 On the File menu, click Build. A Build Status window appears, which provides information about the progress of the build and logs any problems that have occurred. If the build is successful, the last line in the Build Status window reads as follows: Product was built successfully. 3 In the Build Status window, click Close.

  • 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

44
Configuring custom products
Building and testing custom products
3
Do one of the following:
Click
OK
to save your changes and close the Product Editor dialog box.
Click
Apply
to save your changes and continue configuring the product
configuration.
4
If prompted, type a file name, and then click
Save
.
Building and testing custom products
You can build and test your custom product before you include it in an
installation package. Symantec Packager stores testable Microsoft Software
Installer (.msi) files in the folder that is specified for the Deploy Packages tab in
Symantec Packager Preferences.
Building custom products
During the build process, Symantec Packager retrieves information from the
product configuration file to determine which files to include in the custom
product, as well as the command-line parameters, installation options, and
custom settings. Symantec Packager then checks the contents of the custom
product for conflicts and errors. If Symantec Packager encounters a conflict, the
build process stops. You must resolve the conflict and repeat the build process.
After you complete the validation process, Symantec Packager creates a
Microsoft Software Installer (.msi) file, which you can use for testing purposes.
Symantec Packager places the .msi file in the folder that is specified for the
Deploy Packages tab. This folder is usually located in the following directory:
\Documents and Settings\<User_Name>\My Documents\Packager\Deployment
Symantec Packager supports installation of pcAnywhere .msi files only. You can
view these files on the Deploy Packages tab if you edit the Symantec Packager
preferences to list supported .msi files.
To build custom products
1
In the Symantec Packager window, on the Configure Products tab, select the
custom product that you want to build.
2
On the File menu, click
Build
.
A Build Status window appears, which provides information about the
progress of the build and logs any problems that have occurred. If the build
is successful, the last line in the Build Status window reads as follows:
Product was built successfully.
3
In the Build Status window, click
Close
.