Novell ADMINSTUDIO 9.5 User Manual page 1162

Hide thumbs Also See for ADMINSTUDIO 9.5:

Table of Contents

Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver

Application Conflict Evaluators (ACEs)

ACE25 checks the entries in the

displayed in the following format:

The [CUSTOM_ACTION_NAME] custom action has a hard coded directory path of [TARGET_PATH] in its Target

Table 13-37 • ACE25 Summary

Conflict Type:

Description:

Resolution Type:

Open the package file in InstallShield Editor, and in the Target field of the CustomAction table, change any hard

coded paths to relative paths.

ACE26 checks the Merge Modules in a package to confirm that they also exist in the Application Catalog.The

ACE26 Warning String is displayed in the following format:

The [MERGE_MODULE_NAME], version [VERSION] Merge Module is included with this package and yet not

imported into the Application Catalog. It is recommended that all Merge Modules be imported into

the Application Catalog.

ACE26 and ACE36, optional

checks merge modules listed in the

These ACEs are provided to encourage you to import Merge Modules into the Application Catalog and, by doing so,

improve the effectiveness of ACE12, which checks for components that contain files that could be replaced by one

of the imported Merge Modules.

table to identify any hard coded paths. The ACE25 Warning String is

CustomAction

Best Practices / Recommended Rules

Checks the entries in the package's CustomAction table to identify any hard coded

paths in the Target field.

If a package has a hard coded path in the Target field of the CustomAction table, a

warning is generated.

Open the package file in InstallShield Editor and change the hard coded paths to

relative paths in the CustomAction table.

Best Practice

ModuleSignature

ACEs, both check for conflicts with Merge Modules. ACE26

table while ACE36 checks the

ADS-0950-UG00

ModuleDependency

AdminStudio 9.5 User Guide

Troubleshooting