Introduction
This step should always be executed as part of the initial analysis of an application performed during the on-boarding. Once the analysis is complete, the following needs to be checked:
- the generated log files need to be reviewed to verify that no errors or warnings which may impact the quality of the results have been produced. For each of the technologies supported by CAST, the log manager will produce a set of statistics to verify the analysis and compare this to the previous analysis.
- the Analysis boundary to ensure that what has been analyzed and saved into the Analysis Services schemas as objects and links is consistent with the intent and scope of the analysis configuration.
- the quality of the analysis.
- the configuration of Modules (important for Dashboards and CAST Imaging).
Validate analysis based on log messages
To check the logs, you can click the View log option in the Job Progress panel:
| Interface in ≥ 2.9 | Interface in older releases (≤ 2.8) |
|---|---|
|
|
Alternatively, you can move to the Console screen if you are not already there:
Then click the Logs option:
Choose the Run analysis log and click View log:
Investigate each log, especially those with error or warning marks:
Review the more common technology level warnings / errors as described in the table below.
| Technology | References |
|---|---|
| C# and VB.NET | .NET - Analysis messages |
| JEE | |
| Mainframe | Mainframe - Analysis messages |
| C / C++ / Pro*C | C and Cpp - Analysis messages |
| SAP ABAP | SAP ABAP - Analysis messages |
| SQL (via SQL Analyzer extension) | SQL Analyzer - errors and warnings |
- Warning messages will be flagged with a yellow triangle - these require further investigation:
Click to enlarge
- GUID duplicate found - this message in the logs indicates that duplicate objects have been found during the analysis (perhaps two identical source code files have been delivered and only one is used). If this message is seen, analysis results may be inaccurate for the objects in question and you should therefore check for any duplicate files and if any are found, remove them, re-deliver the source code and action a new analysis.
- HEYHO / COOL - messages such as those listed below seen with a "WRN" message level should be ignored as they are internal messages that were inadvertently exposed in the log (this has been fixed in AIP Core ≥ 8.3.46):
HEYHO ! Dependency from X/X to Y/Y could not be added using Classpath Cool ! Dependency from X/X to Y/Y was added using Classpath
Validate Modules and content
To validate the configuration of Modules in your Application (Modules are used extensively in the CAST dashboards / CAST Imaging and other CAST features as a means to configure analysis results for a given Application into meaningful groups or sets for display purposes), move to the Console screen if you are not already there:
Then access the Application - Config - Modules screen to view all the Modules that have been created for the Application during the analysis. First check that all Modules you require are present. By default a "Per Technology" strategy is in place (one module for each specific technology) unless you have opted for a legacy step-by-step onboarding, in which case a "full content" strategy is used (one module for the entire application):
Then, to check the content of the Modules, click the Edit button next to the Module you want to inspect:
Click the Check Content button to load the content of the Module direct from the Analysis schema:
Objects matched by the Module and filters will be displayed in two panels to the right:
| Summary | Displays a list of objects matched by the filter (by object type and number of objects matched). |
|---|---|
| Details | Displays a detailed list of each object matched by the filter, including Name, Full Name and Path. |
Click to enlarge
