Symantec 14541094 Implementation Guide - Page 78

Testing packages, Build, Close

Get Symantec 14541094 - pcAnywhere Host & Remote PDF manuals and user guides
UPC - 037648640480
View all Symantec 14541094 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 78 highlights

78 Configuring installation packages Building and testing packages After completing the validation process, Symantec Packager creates a selfextracting executable file and places it on the Deploy Packages tab for testing and distribution to licensed users. See "Deploying installation packages" on page 79. To build packages 1 In the Symantec Packager window, on the Configure Packages tab, select the package definition file that you want to build. 2 On the File menu, click Build. The Package Build Status window appears, which provides information about the progress of the build and logs any problems that have occurred. If the package build is successful, the last line in the Package Build Status window reads: Package was built successfully. 3 In the Package Build Status window, click Close. Testing packages It is important to test packages before you deploy them to end users to ensure proper functionality. Although some error checking occurs during the build process, some errors cannot be detected until installation. This is especially true if the package includes a product that requires a third-party product or if the package includes a custom command. During installation, Symantec Packager checks for product conflicts and verifies that required products are present on the target computer. The installation fails if Symantec Packager encounters a conflict that it cannot resolve. Test packages to verify that product requirements are met and that the installation sequence is correct. You should open each installed program to ensure that it functions correctly. Ensure that the features that you want are present. This step is especially important if you customized a product to reduce the installation footprint. Product testing ensures that you have not overlooked an important feature. Once you thoroughly test the package, you can deploy it to end users. See "Deploying installation packages" on page 79.

  • 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
78
Configuring installation packages
Building and testing packages
After completing the validation process, Symantec Packager creates a self-
extracting executable file and places it on the Deploy Packages tab for testing
and distribution to licensed users.
See
“Deploying installation packages”
on page 79.
To build packages
1
In the Symantec Packager window, on the Configure Packages tab, select the
package definition file that you want to build.
2
On the File menu, click
Build
.
The Package Build Status window appears, which provides information
about the progress of the build and logs any problems that have occurred. If
the package build is successful, the last line in the Package Build Status
window reads: Package was built successfully.
3
In the Package Build Status window, click
Close
.
Testing packages
It is important to test packages before you deploy them to end users to ensure
proper functionality. Although some error checking occurs during the build
process, some errors cannot be detected until installation. This is especially true
if the package includes a product that requires a third-party product or if the
package includes a custom command.
During installation, Symantec Packager checks for product conflicts and verifies
that required products are present on the target computer. The installation fails
if Symantec Packager encounters a conflict that it cannot resolve. Test packages
to verify that product requirements are met and that the installation sequence is
correct.
You should open each installed program to ensure that it functions correctly.
Ensure that the features that you want are present. This step is especially
important if you customized a product to reduce the installation footprint.
Product testing ensures that you have not overlooked an important feature.
Once you thoroughly test the package, you can deploy it to end users.
See
“Deploying installation packages”
on page 79.