Testing for Conflicts Between Packages

AdminStudio 2021 | 21.0 | Application Manager

Edition:Application Manager is included with AdminStudio Professional and Enterprise Editions.

To identify conflicts between packages or groups of packages in the Application Catalog, perform the following steps.

To identify conflicts between packages already in the Application Catalog:

1. Open Application Catalog and select the Analyze tab of the ribbon.
2. In the Application Catalog tree, select the source package (or group of packages) that you want to test and click the Conflict Wizard button in the ribbon (or right-click on the package and select Conflict Wizard from the shortcut menu). The Target Information panel of the Conflict Wizard opens.

Tip:When performing conflict analysis using multiple source packages and one or more target packages, Application Catalog will evaluate each source package against each target package. However, if you want Application Catalog to also perform conflict analysis of each source package against every other source package and each target package against every other target package, select the root group in the Application Catalog tree (which is, by default, named the Applications group) and then click the Launch Conflict Wizard button on the Analyze tab of the ribbon.

3. On the Target Information panel, select the packages or groups of packages that you want to use as the target in conflict analysis.

Note:If you select the same packages as both source and target, the Next button will be disabled and you will be unable to proceed.

4. Click Next. The Summary panel opens.
5. Review the options selected in the Summary panel and click Finish to begin the conflict identification process. Testing is initiated and messages are displayed in the Output window. When testing is finished, a message appears in the Output window listing how many warnings and errors were generated.
6. View the test results, as described in Viewing Application Conflicts Test Results.
7. Resolve any issues that were detected, as described in Resolving Issues.

See Also