Performing An Ad-Hoc Import Of Transform Files Or Patch Files - Novell ADMINSTUDIO 9.5 User Manual

Chapter 6: Managing Application Catalog Databases
Importing Data
• ProductCode
GUID, for example:
{12345678-1234-1234-1234-123456789012}
•
Product
not authored into the database.
•
ProductVersion—Version of the product in string format. The format of the string is: major.minor.build.
•
List of Transform
•
[None
Product Name identifier to determine if a package is a duplicate.
4. Click OK to save your changes and exit the Options dialog box
5. Proceed with the package import, as described in
Note • If Application Manager is performing a bulk import or reimport, it still identifies duplicate packages using the
user-specified criterion. Application Manager will generate a unique displayed product name and allow the import to
proceed without prompting the user.
Note • The options that you select on the Duplicate Package tab of the ConflictSolver and Application Manager
Options dialog box apply globally to all packages that you attempt to import; you cannot apply different identifiers
to different packages. Also, since these options are saved in the AdminStudio Shared Directory, everyone using
AdminStudio at your organization will share the same Duplicate Package options.

Performing an Ad-Hoc Import of Transform Files or Patch Files

Edition • You can only perform an ad-hoc import if you are connected to a Software Repository-enabled
Application Catalog. The Software Repository feature is included in AdminStudio Enterprise Edition.
In a large enterprise, transform and patch files are created frequently to modify packages for different situations in
their organization. For example, to localize a software application, a transform file is often created for each
language supported by that application. Systems Administrators in these large enterprises have to keep track of
which software package each file is supposed to be applied to.
You cannot tell which package a transform or patch file is associated with by just looking at the file. However, you
can use the Import Wizard to perform an ad-hoc import of these loose transform and patch files into your
Application Catalog. Then, Application Manager will:
•
Determine which of the packages in the Application Catalog the transform or patch file is associated with, and
•
Store the files in the Software Repository along with that package's other associated files.
234
Property—Unique identifier for the particular product release, represented as a string
Language—The language the installer should use for any strings in the user interface that are
Files—A list of the transformations associated with this package.
Selected]—If you do not select any of these five identifiers, Application Manager checks the
Importing Windows Installer
ADS-0950-UG00
Packages.
AdminStudio 9.5 User Guide