Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
ConflictSolver Reference
AdminStudio 9.5 User Guide
ADS-0950-UG00
1247
Click Next to proceed to the Custom Options Panel or the DLL-Based ACEs Panel; click Back to return to the
General Information Panel.
Rule Type
Specify the type of ACE you are creating:
•
Custom - Source Only Packages ACEs
allow you to quickly test any column or any
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
for more information.
•
Custom - Source and Target Packages ACEs
allow you to compare columns or
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
for more information.
•
DLL - User Provided DLL Based ACEs
allow you to run more complex tests—testing
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
Conflict Application
Resolution Definitions (CARDs)
to fix the conflict. See
Creating a User Provided DLL-
Based ACE
.
Table 13-102 •
Additional Information Panel Option (cont.)
Option
Description
Summary of Contents for ADMINSTUDIO 9.5
Page 1: ...AdminStudio 9 5 User Guide Version 9 5...
Page 50: ...Contents 50 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 52: ...52 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 156: ...156 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 440: ...440 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1090: ...1090 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1426: ...1426 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1686: ...1686 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1794: ...Chapter 24 AdminStudio Public API Reference 1794 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1842: ...Index 1842 ADS 0950 UG00 AdminStudio 9 5 User Guide...
