Types Of User-Defined Aces - Novell ADMINSTUDIO 9.5 User Manual

Types of User-Defined ACEs

In addition to the ACEs included with ConflictSolver, you can also create your own user-defined ACEs to use when
detecting conflicts. You can create three types of ACEs:
Custom - Source Only Packages ACEs
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.
For an example of this type of user-defined ACE, see
Note • ConflictSolver supports external package conflict checking for Custom - Source Only Packages ACEs. The
Source package can be selected from the Application Catalog Database or from an external MSI package.
Custom - Source and Target Packages ACEs
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 an 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.
For an example of this type of user-defined ACE, see
Note • 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 Application Catalog Database.
DLL - User Provided DLL Based ACEs
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 Definition (CARD)
to fix the conflict.
For an example of this type of user-defined ACE, see
AdminStudio 9.5 User Guide
Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
ADS-0950-UG00
Creating a Custom/Source Only Packages
Creating a Custom/Source and Target Packages
Creating a User Provided DLL-Based
Application Conflict Evaluators (ACEs)
ACE.
ACE.
ACE.
1175