Novell ADMINSTUDIO 9.5 User Manual page 1097

Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
Best Practices for Conflict Detection
Use the Command Line / Bulk Import Option of ConflictSolver
ConflictSolver supports a bulk import process, which allows you to import multiple installer packages (such as
MSI, MSM, MST, MSP , OSC and NCP files) at once without any user intervention. You can set up these files and
have them run overnight or on an unattended workstation. By doing this, you minimize the need for someone to
monitor the import process, freeing that person up to perform other tasks.
Also, if you use Bulk Import to import packages before they have been conflict checked, ConflictSolver
performance is improved because it is quicker to perform conflict detection between internal installation packages
than between internal packages and an external MSI package.
Performing a Bulk Import
To perform a bulk import, use the following command line:
iscmide.exe -I -C"c:\mypackages\myconfig.ini"
If you are using a configuration file, the only necessary parameters to pass at the command line are and
-I -
. You can include all other parameters inside the INI file. The following INI file is
C"configuration_file_name.ini"
used to import packages into an SQL Server Application Catalog for a named user:
[General]
DatabaseType=SQL
LogFile=c:\temp\importlog.txt
MSIFile=3
MSMFile=1
[SQL]
Server=ConflictSolverSQL2K
UserID=Admin
Password=mypassword
Database=AdminStudio70
[MSIFile-1]
File=\\server\Data1.msi
Transform1=\\server\Data1a.mst
Transform2=\\server\Data1b.mst
Group=OfficeApps
[MSIFile-2]
File=\\server\Data2.msi
Group=OfficeApps\Secondary
[MSIFile-3]
File=\\server\Data3.msi
[MSMFile-1]
File=\\server\CrystalReports.msm
For more information on command line options, see Application Manager Command-Line Functionality and
Application Manager Configuration File.
AdminStudio 9.5 User Guide ADS-0950-UG00 1097