Mar. 28, 2016
AppDNA uses the external data during the analysis process, looking for matching applications in the external data sources. When there is a match between the application being analyzed and the application record in the external data source, AppDNA overwrites the application's standard RAG value or adds an overlay or icon to the standard RAG icon, depending on the trust level applied to the external data source.
Currently AppDNA provides two different types of external data:
Readiness lists – These are based on application compatibility lists provided by Microsoft to IT professionals. Applications that are marked as compatible in this list have been verified as working on the target platform by the software publisher or the Microsoft Windows logo testing program. AppDNA matches applications in AppDNA with applications in the list by the name, manufacturer, and version. By default this matching is case insensitive and ignores white space – but you can configure this. External data icons that derive from a readiness list indicate the following:
PCA (shim) databases – These are based on Microsoft's system application compatibility database, which is part of the Program Compatibility Assistant (PCA) that is built-in to the operating system. Unlike the readiness lists, AppDNA does not match applications based on the name, manufacturer, and version. Instead, AppDNA matches executable (.exe) files within the application to executable files listed in the database. External data icons that derive from a PCA database indicate the following:
|Data source||Applies to|
|Microsoft Vista App Readiness List||Windows Vista SP2, Windows Server 2008 SP2|
|Microsoft Vista Shim Database||Windows Vista SP2, Windows Server 2008 SP2|
|Microsoft Windows 7 App Readiness List||Windows 7 SP1, Windows Server 2008 R2 SP1|
|Microsoft Windows 7 Shim Database||Windows 7 SP1, Windows Server 2008 R2 SP1|
|Microsoft Windows 8 App Readiness List||Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2|
|Microsoft Windows 8 Shim Database||Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2|
This removes any existing external data journal entries for the affected applications and creates new external data journal entries. AppDNA automatically applies the external data to applications when they are first analyzed. Generally it is therefore only necessary to use this tool when you have explicitly made changes to the configuration of a data source or have changed the trust level.
AppDNA uses the journal mechanism to handle external data. When AppDNA applies the external data to your application portfolio, it creates a special external data journal entry for each matching application and report combination. If necessary, you can delete individual external data journal entries in the Journal screen.
AppDNA can show only one icon that derives from the journal mechanism on an application's RAG status in the report views. This means that if you add a Compatible, Known issues, or Incompatible manual journal entry after an external data journal entry was created for the same application and report combination, the manual journal entry's icon overwrites the application's RAG status in the report views and the external data journal entry's icon is not shown. (If you want to add a manual journal entry – for example, to record testing notes – but you do not want it to overwrite the application's RAG status, use the Unknown journal entry type.)
You can convert an individual external data entry for an application to a standard journal entry. This means that the application's RAG status will be overridden by the corresponding compatibility (journal) icon.
The Remediation report view for that application opens.