Performing an Ad-Hoc Import of Transform Files or Patch Files
AdminStudio 11.0
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. |
Note: You can only perform an ad-hoc import if you are connected to a Software Repository-enabled Application Catalog. See Using the Software Repository for more information.
Note: To perform an ad-hoc import of a transform file or patch file, the package that the file is associated with must exist in the Application Catalog. If no associated package exists, the file cannot be imported.
To perform an ad-hoc import of a transform or patch file:
|
1.
|
Open Application Manager. |
|
2.
|
Connect to a Software Repository-enabled Application Catalog. |
|
3.
|
On the Catalog tab of the Application Manager ribbon, click Import. The Welcome panel opens. |
|
4.
|
Click Next. The File Selection panel opens. |
|
5.
|
Select the transform or patch file that you want to import. |
|
6.
|
Select the Add the file(s) to the Software Repository option. |
After you select this option, the Additional Dependencies of the Import File list appears, enabling you to select any dependencies of the file you are importing. For example, a dependency might be a file that the transform file references that is stored externally in a separate CAB file.
|
7.
|
Select dependencies, if desired, and click Next. |
|
8.
|
The Target Package Information panel opens and lists the package that Application Manager has determined is associated with this file. |
Note: For transforms and patches, if Application Manager determines that there are no packages associated with this file, you cannot proceed with the import.
|
9.
|
Select the file’s associated package. |
|
10.
|
If you want to reimport a new version of this package along with the file you are importing, select the Reimport new version of the package with this file change option. If you do not select this option, the package will not be reimported. |
|
11.
|
Click Next. The Summary panel opens, listing the Adhoc file to import, the Destination Packages for the file, and whether you chose to reimport the package. |
|
12.
|
Review the information in the Summary panel. If you are satisfied with the import options, click Finish to start the import. Progress messages appear in the Output Window. |
Open topic with navigation