Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0, Справочник

Страница: 25 / 302

Wise Package Studio Reference 25
Introduction to Wise Package Studio
Directory Contents
000, 001, and so on
(Not available in Standard
Edition.)
Source files that are associated with each package’s installation. The
subdirectories are numbered sequentially. These subdirectories are created when:
z
You distribute a package to the share point directory.
z
You import a package into the Software Manager database, and you distribute
source files.
See How Source Files Are Indexed on page 27 and About .QUE Files in the
Software Manager Help.
Available Packages
(Not available in Standard
Edition.)
Provides a centralized location for storing all packages that are available for
deployment, keeping them separate from packages that are still in development.
A separate subdirectory, named application\package, is created for each package.
This subdirectory contains the compiled installation file, which is read-only, and
any files needed for the installation, such as external .CAB files or SMS package
definition files. This subdirectory is created when you change the package’s status
to Available.
Custom Actions See Installation Resources and Their Locations in the Windows Installer Editor
Help.
Languages See Installation Resources and Their Locations in the Windows Installer Editor
Help.
Merge Modules See Installation Resources and Their Locations in the Windows Installer Editor
Help.
Projects Project information, including installation files, SetupCapture reports, and
transform files. Information for each project is stored in a separate subdirectory.
You define the subdirectory name when you create the project. The subdirectory is
created the first time you open the project on the Projects tab.
Package definition files (.WPF) and their defined files. Each package definition file
is stored in its own subdirectory. This subdirectory has a Files subdirectory where
the files specified in the package definition file are copied.
Reports
(Not available in Standard
Edition.)
The Report.ini file, which stores information about the predefined reports and,
with Enterprise Management Server, any report customizations.
The ReportConfig.ini file, which is used when saving a ConflictManager report
directly to a file without it opening in a report viewer.
Resources See Installation Resources and Their Locations in the Windows Installer Editor
Help.
Scripts
(Not available in Standard
Edition.)
Temporary .QUE files representing packages that have been distributed but not
imported into the Software Manager database. See About .QUE Files in the
Software Manager Help.
This directory also contains the package installation file when:
z
You distribute a package that is not part of a Workbench project.
z
You import a package into the Software Manager database.
With Enterprise Management Server, the Scripts directory also stores information
about package subscriptions.