Software Manager Reference
18
Introduction to Software Manager
Naming Applications and Packages for Other Items
z
Merge module
You might group merge modules by manufacturer or function. Example: Create an
application named MDAC, and then import merge module files to packages named
MDAC 2.5, MDAC 2.6, MDAC 2.7, and so on.
z
Patch
Application name: Use the base package’s application name.
Package name: Describe the patch. Example: Sample_5.01_Update.
z
Transform
Application name: If the transform is applied to a blank database, you might give it
a unique application name, or group all such transforms under one application name
(example: General Application Registration Transforms). If the transform is applied
to a base package, use the base package’s application name.
Package name: Describe the transform. Example: If the base installation’s
application name is Sample, and the transform changes the language of the
installation dialog boxes to French, name the transform package Sample_French.
About Package Meta Data
Expand the value of the Software Manager database by using meta data to store
package information that is not otherwise recorded when the package is created.
z
You can view meta data in the Package pane in Software Manager, provided
Package Pane is marked on the Meta Data Fields dialog box.
z
You can view meta data on the Package Attributes dialog box.
z
You can add meta data to custom reports as you would any other data in the
Software Manager database.
from the share point
directory
the application and package names that were
specified during Package Distribution. If the
application and package names were not specified
during distribution, they are assigned as described
below.
multiple Windows Installer
installations
The product name and version from the Product
Details page in Windows Installer Editor. Application
name = product name. Package = product name +
version. Example: If the product name is Sample and
the version is 1.0.0, the application name will be
Sample and the package name will be Sample 1.0.0.
z
multiple Windows
Installer installations
that do not have a
product name and
version, or
z
multiple WiseScript
installations
the file name. Example: If you import Sample.msi, the
application name and package name will both be
Sample.
When you import
the application/package names are obtained
from:
Summary of Contents for SOFTWARE MANAGER
Page 1: ...Software Manager Reference...