Table of Contents
Advertisement
About Applications and Packages
Software Manager Reference
repackage internally developed applications and lets them focus on other activities. It
also assures the deployment team that applications will perform as expected and
reduces calls to the help desk.
Process for Sharing the Software Manager Database
1.
During development, the developer imports a new application to the shared
Software Manager database. The developer can view resources used by applications
that are in development and those that have been deployed.
2.
When development is finished, the developer notifies a member of the deployment
team.
3.
The deployment process begins.
Note
Because applications that are still in development will be mixed with those that have
been tested and deployed, members of the deployment team must be careful not to
deploy applications that are still in development.
See also:
Installation Resources and Their Locations in the Windows Installer Editor Help
When you add a package to the Software Manager database, you assign it an application
name and a package name. An application is a group of similar packages. Packages
represent different versions of a single application installation, or different components
of a larger suite. Group packages that are not likely to coexist on the same computer
under a single application. This prevents you from seeing resources that are not relevant
to a specific application. Also, because ConflictManager does not look for conflicts
between packages of the same application, this speeds the conflict detection process
and avoids showing you conflicts that are not relevant.
Example:
Your Software Manager database might contain three Microsoft Office packages: Office
97, Office 2000, and Office XP. Because you are not likely to install multiple versions of
Microsoft Office on a single computer, you can group them under one application,
named Microsoft Office.
Obtaining Application and Package Names for Installations
If the package's meta data is in the Software Manager database, the application and
package names are pre-filled during import.
Otherwise, they are assigned as described below.
When you import
a single installation file (any
type)
Introduction to Software Manager
the application/package names are obtained
from:
prompts during import.
17
Advertisement
Table of Contents
