Importing From The Share Point Directory - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Hide thumbs Also See for SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0:
Table of Contents

Advertisement

Importing From the Share Point Directory

Software Manager Reference
Group patches and transforms to determine the collective impact of those
patches or transforms during testing and deployment.
Easily deploy patches and transforms with distribution systems.
If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise
Connector to import the patch or transform from the Software Manager database into
Software Management Framework. Wise Connector imports the patch or transform
when it imports the base MSI package. You can then use Software Management Solution
to deploy the patch or transform.
Defining the State of the Base Package
When you import a patch or transform, you can specify additional transforms to be
applied to the base package before the patch or transform you are importing. This
changes the state of the base package, which determines the resources that are
included in the imported patch or transform package and changes how it behaves when
it is installed.
Example: Suppose that two different transforms can be applied to a base package.
The Base Package installs File A, File B, and File C.
Transform 1 deletes File C.
Transform 2 installs Registry Key X and modifies File C.
When you apply the transforms like
this:
Base Package
Transform 2
Base Package
Transform 1
Transform 2
See:
Importing a Windows Installer Patch File
Importing a Transform File
Package Groups
on page 87
When the Database pane displays a number of packages that are queued for import, use
the Import from share point directory option in the Import Wizard to import the
packages into the Software Manager database.
When a package is distributed to the share point directory, the package and its source
files are copied to several subdirectories of the share point directory, and a .QUE file is
created to represent the package that is waiting to be imported into the Software
Manager database.
When a package is created with Package Definition and not imported directly into the
Software Manager database, the package definition file (.WPF) is saved in the share
point directory, its files are copied to the share point directory, and a .QUE file is
created.
Transform 2 does this during
installation:
installs Registry Key X
modifies File C
installs Registry Key X
File C is not present, because the state of
the Base Package has been changed by
applying Transform 1.
on page 51
on page 48
Importing Packages
37

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

This manual is also suitable for:

Software manager 8.0

Table of Contents