User Guide

36
Using the Enterprise Edition
Share Point Directory Contents
! Resources that are used to create Windows Installer installations. Examples:
installation templates, component rules, language files, and so on.
! Predefined reports.
! Temporary .QUE files representing packages that have been distributed but not
imported into the Software Manager database.
! Source files of installations you import into the Software Manager database.
! The default Microsoft Access-based Software Manager database, if you choose to
install it.
If your organization uses Wise Package Studio, the share point directory might contain
additional information that is unique to that product.
For a list of the share point subdirectories and their contents, see Where are Installation
Resources Stored? on page 32.
Deleting Files From the Share Point Directory
Caution
Do not edit or delete the contents of the share point directory or its subdirectories outside of
Wise for Windows Installer or other Wise Solutions tools. Doing so will cause problems in
Software Manager and can result in loss of data.
A common question is “Can I clean up the share point by deleting unused source files?”
The answer is no. It is too difficult to know which files are safe to delete.
The only recommended way to delete files from the share point directory is to delete the
entire package from the Software Manager database. When you do so, you can delete
the package’s source files from the share point subdirectories (000, 001, and so on), if
those files are not referenced by any other application. See Deleting a Package in the
Software Manager Help.
Also see Sharing Installation Resources on page 34.
How Source Files Are Indexed
A sequentially-numbered directory structure is created under the share point directory
to store occurrences of installation source files when:
! You distribute a package to the share point directory.
! You import a single package or multiple packages to the Software Manager database,
and you distribute source files.
An index file named wamdb.idx, located in the share point directory, records the location
of the source files. Because files are indexed, distributing source files to the share point
eliminates storage of duplicate files and results in smaller storage requirements than if
you distribute to a network directory.
Example:
Suppose you have 3 packages, each containing a version of report.dll. The first time you
distribute a package containing report.dll, the file is placed in the share point’s 000\001
directory. If you distribute another package containing the same version of report.dll,
the file is not saved a second time, but a counter is set for that file in wamdb.idx. If you
distribute a third package that uses a different version of report.dll, the file is stored in a