Running Conflict Identification Again; Deleting Persisted Conflict Data; Conflict Persistence - Novell ADMINSTUDIO 9.5 User Manual

Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
Identifying and Resolving Conflicts

Running Conflict Identification Again

At times, it may be necessary to run conflict identification again on a package that you have previously checked for
conflicts. This could be because other packages you previously compared this package against have changed. It
may be because you have added additional packages to ConflictSolver.
There are two ways to accomplish this.
•
If you want to run conflict identification again using the same options as the last time you ran conflict
identification on the package, you can do so by clicking the Run Again button from the package's
View.
•
In all other cases, use the
Note • When you run conflict identification for a package on which you have previously performed conflict
identification, the persisted conflict data is deleted and replaced with the new conflict data.

Deleting Persisted Conflict Data

Task: To delete persisted conflict data from a package:
1. Right-click on the package in the Product View, point to Delete, and select Persisted Conflict
Information.
2. Confirm the deletion.

Conflict Persistence

ConflictSolver automatically persists conflict information for packages in ConflictSolver, and for the last execution
of the Conflict Wizard between an external package and packages already in ConflictSolver. This enables you to
run conflict identification between packages without having to perform the resolution immediately.
Your workflow may, for example, dictate that you import several packages into ConflictSolver first (placing them in
some sort of staging group) and then perform conflict identification on them all at once. Resolution of identified
conflicts may be much later in the workflow. ConflictSolver assists you by retaining the conflict information until you
are ready to work with it.
Each package in ConflictSolver includes a
can see when conflict identification was performed, between which packages, using which ACE rules, and the
result. You can also see which packages have been updated, added to, or deleted from ConflictSolver since
conflict identification was performed.
1118
Conflict Wizard to perform conflict identification.
Conflicts View, where this persisted conflict data can be accessed. You
ADS-0950-UG00 AdminStudio 9.5 User Guide
Conflicts