Novell ADMINSTUDIO 9.5 User Manual page 1247

Table 13-102 • Additional Information Panel Option (cont.)
Option
Rule Type
Click Next to proceed to the Custom Options Panel or the DLL-Based ACEs Panel; click Back to return to the
General Information Panel.
AdminStudio 9.5 User Guide
Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
Description
Specify the type of ACE you are creating:
•
Custom - Source Only Packages ACEs
value of a table to support your business logic. For example, you could use a user-
defined ACE to identify packages that create a desktop icon. To define a Source Only
Packages ACE, you must define an SQL "Where" clause.
ConflictSolver supports external package conflict checking for Custom - Source Only
Packages ACEs. The Source package can be selected from the ConflictSolver
Application Catalog Database or from an external MSI package.
See Creating a Custom/Source Only Packages ACE
• Custom - Source and Target Packages ACEs
values of Source package tables (new packages that you want to install onto a user's
system) to columns or values of Target package tables (packages already installed on a
user's system).
For example, you could use a Source and Target Packages ACE to determine if the
installation of a Source package onto a Target system would overwrite or conflict with
an existing entry in the .ini file in the System directory of the Target system.
To define a Source and Target Packages ACE, you must define a SQL "Where" clause,
and specify a Join Column—a table column in the Application Catalog database that
has a matching value for both the Source and Target packages. Rows in each of the
packages that have a matching value in the Join Column are selected and those rows
are checked against the Source and Target Packages.
ConflictSolver does not support external package conflict checking for Custom -
Source and Target Packages ACEs. Both the Source and Target Packages must be
selected from the ConflictSolver Application Catalog Database.
See Creating a Custom/Source and Target Packages ACE
•
DLL - User Provided DLL Based ACEs
many tables in any combination. For example, you could use a DLL-Based ACE to
confirm that a source product language is the same as all target product languages. To
define a DLL-Based ACE, you use SQL and various programming languages to
construct a Windows DLL. With DLL-Based ACEs, you can use a
Resolution Definitions (CARDs)
Based ACE.
ADS-0950-UG00
allow you to quickly test any column or any
for more information.
allow you to compare columns or
allow you to run more complex tests—testing
to fix the conflict. See Creating a User Provided DLL-
ConflictSolver Reference
for more information.
Conflict Application
1247