Software Manager Reference
16
Introduction to Software Manager
See also:
About the Wise Software Repository
on page 14
Sharing the Software Manager Database With Wise Package Studio
on page 16
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:
z
You distribute a package to the share point directory.
z
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 three 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 second directory, 000\002. The result is a set of all the unique
source files used by all the packages in the Software Manager database.
See also:
About the Share Point Directory in the Windows Installer Editor Help
Copying an Installation to the Share Point Directory in the Windows Installer Editor Help
Importing From the Share Point Directory
on page 27
Sharing the Software Manager Database With Wise Package Studio
Developers can use the Software Manager database solely to store information about
applications they develop. This situation is typical of an independent software vendor
(ISV) environment. Developers who create applications for internal, corporate use might
want to obtain information about external applications that have been tested and
deployed throughout their organization.
If the development team in your organization uses Wise Installation Studio, developers
can connect to the deployment team’s Software Manager database.
Why share information in the deployment Software Manager database? Because the
Software Manager database used by Wise Package Studio contains approved versions of
applications that have been deployed, developers can use this information to build
installations that adhere to corporate standards.
Example:
By checking the Software Manager database when building an installation, and selecting
source files from the database, developers can be sure to use the correct versions of
critical files (examples: the Visual Basic runtime or MDAC). The result is that developers
produce more reliable installations that will not conflict with applications already
deployed to end-users’ computers. This eliminates the need for the repackaging team to
Содержание SOFTWARE MANAGER
Страница 1: ...Software Manager Reference...
