Importing Multiple Merge Modules Simultaneously; Simultaneously Importing Windows Installer Packages And Merge Modules; Using The Command Line To Import All Packages In A Directory - Novell ADMINSTUDIO 9.5 User Manual

Chapter 6: Managing Application Catalog Databases
Reference

Importing Multiple Merge Modules Simultaneously

The best way of importing multiple merge modules simultaneously into an Application Catalog is via a
configuration file. Use the following command line to call your configuration file, in which you can specify multiple
merge modules to import.
iscmide.exe -C"configuration_file"
Replace
configuration_file
locations of the merge modules you want to import.

Simultaneously Importing Windows Installer Packages and Merge Modules

To simultaneously import both Windows Installer packages and merge modules into an Application Catalog, use a
configuration file from the command line. In this configuration file, you can specify the names and locations of both
merge modules and Windows Installer packages you want to import.
Use the following command-line to specify your configuration file:
iscmide.exe -C"configuration_file_name"
Replace
configuration_file_name

Using the Command Line to Import All Packages in a Directory

It is possible from the command line to import all packages in a directory. This can be done by placing the
following line in a batch file (modifying it as necessary for your specific environment):
for %%a in (*.msi) do ISCMIDE
-S"server_name"
-U"userid"
-P"password"
-D"Application_Catalog_Name"
-IF"%%a"
-Q
-L"%%aLog.txt"
The above statement runs Application Manager, importing each MSI package in the Application Catalog, and
creates a log file with the name of the
However, the above command makes the following assumptions:
•
ISCMIDE.exe
•
All packages are being imported into the specified SQL Server Application Catalog (provide the server name,
userid, password, and Application Catalog name with the appropriate parameters
respectively).
•
The above command will start Application Manager, import a file, exit Application Manager, and then restart
Application Manager for each MSI file. If this is not acceptable, use a configuration file instead.
•
No transforms are applied to the imported packages. If you need to apply transforms, use a configuration file
instead.
434
with the name and location of the configuration file containing the names and
with the name and location of the configuration file to use.
.msi
is in the path; otherwise, include the full path to
file prepended to the log file name.
ISCMIDE.exe
.
, ,
-S -U -P
ADS-0950-UG00 AdminStudio 9.5 User Guide
, and ,
-D