Introduction
Use the a variety of means to check for alerts and consult log messages:
Missing dependencies/JAR file alerts
"Missing dependencies/JAR file" type alerts, are particularly important for the accuracy of the overall analysis results - for example if JAR files referenced in the source code (for example via a Maven pom.xml file) cannot be found then some objects will not be created, links will be missing, transactions will be incomplete etc. It is therefore crucial to check your configuration to avoid these alerts.
These alerts generally indicate that the source code is incomplete, that there is a configuration issue or simply that there is something wrong in the source code. If these alerts are not dealt with, then there is a risk that the source code analysis will be erroneous or may not even complete. It is up to you to manage these alerts:
- some can be easily fixed by:
- altering the source code package configuration (for example the root folder may be incorrect)
- by including the missing items in the source code ZIP file or by ensuring that access to the third-party items is available - see Configuring source code delivery for Maven and Configuring source code delivery for .NET
- some may be more difficult to fix and you may need to alter your original source code
Example alerts:
| Undefined variable | A variable has been discovered in the source code. Console cannot detect a value for this variable and therefore an alert has been created. |
|---|---|
| Missing project | A reference to a package, project, library file, folder or resource has been discovered in the source code package. Console cannot detect this specific item anywhere in the source code and therefore an alert has been created. |
| Missing library file | |
| Missing folder | |
| Missing resource | |
| Please note that if you exclude a folder and subsequently Console finds a reference to the excluded folder, then an Alert will be generated. If you absolutely need to exclude the folder and want to avoid an alert, you can exclude the folder contents only using a specific Regular Expression. For example, you have a subfolder entitled "unittests" that you must exclude, however, other code references this folder and as such an Alert will be generated during the source code scan when the version is created. Use forward slashes around the folder name in your Regular Expression to force Console to ignore the contents of the folder but keep the folder itself: /unittests/ | |
Interface in ≥ 2.9
If any alerts are triggered they will be displayed on the left side of the Job Progress panel:
Click to enlarge
Interface in older releases (≤ 2.8)
If any are found, a warning icon will be displayed in the Configure section:
Clicking the View Log option to go straight to the log file to see the missing dependencies alerts. See also Validate dependency configuration. For example, the following image shows a list of packages that are referenced in the delivered source code and which were not found. In the situation shown in the example below, the correct Maven repository needs to be defined in Administration Center - Settings - Maven Repositories:
Click to expand
Missing packages (rather than missing classes) are listed in alphabetical order.
Log messages
Logs option
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
Job Progress panel
Alternatively you can access logs directly from the Job Progress panel:
Interface in ≥ 2.9
Interface in older releases (≤ 2.8)
Click the View log option in the Progress window:
