Symantec SOFTWARE MANAGER 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual page 30

Software Manager Reference
Distribute source files to the share point directory
Mark this to copy all source files to a single, centralized location.
Clear this check box to import the package description into the Software
Manager database without copying its source files to the share point directory.
Warning
Distributing source files for a package that represents a Visual Studio integrated
project breaks the integration with the Visual Studio solution.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the
same application and package names.
If you clear this check box and the application and package names are already
in the database:
If the existing package has resources, the new package is not imported.
If the existing package does not have resources, the new package's
resources are added to the existing package. An existing package might not
have resources if it consists only of meta data.
Do not modify the original package
Normally, when you import a Windows Installer installation (.MSI or .WSI), the
original installation file is updated with Wise-specific version information that
speeds future subscriptions and imports of the installation. Mark this to prevent
the original file from being changed.
6. To assign the imported package to one or more groups:
a. Click Groups on the Import Type page. The Select Groups dialog box appears.
b. Mark the check boxes of the groups to assign the package to.
c. Click OK.
7. Click Next on the Import Type page.
The Package Details dialog box appears.
8. Complete the dialog box:
.MSI/.WSI File
The file you specified is displayed.
Application Name
To create a new application, enter a unique name. To add this package to an
existing application, select an application from the drop-down list.
Note
If the package's meta data is in the Software Manager database or the package
was created in Wise Package Studio, Application Name and Package Name
are pre-filled. In that case, don't change these names. Otherwise, you will have
two packages in the database for the same installation: a package with just
meta data and the package you import.
For information on application and package names, see
Packages on page 17.
Importing Packages
About Applications and
30