Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference page 33

Software Manager Reference
See Adding Meta Data to the Software Manager Database in the Windows Installer Editor
Help.
Importing a Package Definition
When you use the Package Definition tool in Workbench to create a package, and you
mark the Import into Software Manager check box:
A record for the package is created in the Software Manager database.
The package status is set to Under Development.
Resources are not added. Typically, a package that you create in this way doesn't
have resources, because the package might consist of a single file or command line.
See Creating a Package Definition File in the Wise Package Studio Help.
Importing Package Resources
When you use the Import Wizard in Software Manager, or when you use the Auto Import
Service:
If the package is not already in the Software Manager database, it is added along
with its meta data.
Information about the package's resources is added to the database.
Depending on the import options you select, the resources themselves might be
copied to the share point directory and their source paths updated in the
installation.
This lets other team members view and share resources from the package. It also lets
you manage the package in Software Manager and resolve conflicts.
See Package Import on page 34.
When to Add Packages to the Software Manager Database
Typically, you add packages to the Software Manager Database when certain milestones
in the repackaging process are reached. Develop corporate standards for these
milestones. Your Wise Package Studio process templates should reflect these standards
and ensure that the importing occurs at the appropriate time.
Recommendations:
When the installation is first created, add its meta data.
When the installation is ready for conflict management and testing, import its
resources.
(For corporate developers.) When the installation is ready for release, import its
resources.
If you import package resources too early in the development process, they are
likely to become outdated. (Example: .DLLs and .EXEs are updated frequently
during a typical development process.) This makes it possible for others to use
those outdated resources in their installations. Consider this when you develop
corporate standards and procedures for importing and sharing resources.
Importing Packages
33