Best Practices For Conflict Detection; Plan Your Import - Novell ADMINSTUDIO 9.5 User Manual

Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver

Best Practices for Conflict Detection

Best Practices for Conflict Detection
When using ConflictSolver, the most database-intensive (and therefore most time consuming) tasks that you
perform are importing packages and performing conflict detection. The time needed to complete these tasks
depends upon how you have configured ConflictSolver and the steps that you follow. To ensure optimal
performance of ConflictSolver during package import and conflict detection, we recommend that you incorporate
the following best practices:
•
Plan Your
data and custom tables. Also, specify that you do not want to check for validation errors or conflicts during
import, and use the bulk import command line process. See
•
Plan Your Conflict
conflict detection by choosing to run only the ACEs that are relevant to your organization. See
Conflict
•
Perform Conflict
detection. See

Plan Your Import

Planning your import consists of the following steps:
•
Check and Configure Your Import Options
•
Use the Command Line / Bulk Import Option of ConflictSolver
Check and Configure Your Import Options
Before initiating an import, you should review the following options on the Import tab of the ConflictSolver
Options dialog box:
•
Import Binary Data & Import Custom
you do not need to import either binary data or custom tables.
•
Check for Validation Errors and Check for
import is often unnecessary. Also, conflict detection at the time of package importation will become an
exponentially slow operation as the size of your Application Catalog increases, since this option causes the
package to be conflict checked against all existing packages in the Application Catalog.
•
Check for Windows
quality validation tests and Windows Installer validation tests on newly imported packages. See
Resolving Package Errors Using
Generally, unless it supports some specific business case, deselect the five import options on the Import tab of
the ConflictSolver Options dialog box.
1096
Import—If you are not using user-defined ACE rules, specify that you do not want to import binary
Detection—Perform conflict detection on internal packages only, and limit the scope of
Detection.
Detection—Follow this sequence of steps to quickly and efficiently perform conflict
Perform Conflict Detection.
Integrity—Select the PackageExpert option on the Import tab if you want to run Vista
Tables—If you do not expect to run user-defined ACE rules, then
Conflicts—Checking packages for validation at the time of
PackageExpert.
Plan Your Import.
ADS-0950-UG00 AdminStudio 9.5 User Guide
Plan Your
Identifying and