Software Manager Reference
33
Importing Packages
Use Transactions for Import
Mark this check box to import installation resources as database transactions
instead of importing them individually. This speeds the import, but can lock
Software Manager database records temporarily during the update. Use this
option if you are the only person importing packages. If multiple people are
importing packages at one time, do not mark this check box.
9. Click Finish.
The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your
work in Wise Package Studio. From this dialog box, you can view a log file for the
import.
The package you selected is imported to the active Software Manager database.
During the import process, errors are displayed as they are encountered.
See also:
Wise Task Manager in the Windows Installer Editor Help
Importing a Transform File
You can import a Windows Installer transform (.MST) into the Software Manager
database from a network or local drive. This creates a separate package for the
transform and keeps the transform’s resources separate from the resources in the base
package.
To add the transform’s resources to the base package instead, apply the transform when
you import the base installation. When you do this, you cannot distribute the transform
as a separate entity.
You can distribute the transform as part of a group for easy deployment by a distribution
system.
See
Creating Package Groups
on page 42.
Note
If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise
Connector to import the transform from the Software Manager database into Software
Management Framework. Wise Connector imports the transform when it imports the
base MSI package. You can then use Software Management Solution to distribute the
package.
See
Importing a Windows Installer File
on page 29.
Options for Applying Imported Transforms
z
Apply the transform to a blank Windows Installer database (schema.msi).
The resulting transform package includes additions only and excludes deletions and
modifications. The transform package has no dependencies. You might use this
option when you have a standard, corporate transform that you apply to all
packages. (Example: General Application Registration Transforms.)
When you apply the transform to a blank Windows Installer database, you cannot
resolve conflicts in or export the transform package.
Summary of Contents for SOFTWARE MANAGER
Page 1: ...Software Manager Reference...
