Application analysis configuration - Config - Analysis
For information about settings related to specific technologies, please see the following pages:
Starting 3.6.0-funcrel, analysis configuration settings for C/C++, JEE and Mainframe are available after an onboarding/fast-scan and before the initial analysis. For all other technologies and releases, analysis configuration options are only exposed after an initial analysis.
File extensions
Each technology exposes a list of file extensions that determines which files the analyzer will process.
Updated in 3.6.7-funcrel
Before the initial analysis, these lists are populated with all the file extensions supported by the discoverers that are installed for the technologies found in the delivered source code. Previously the lists contained a subset of these extensions, which meant that files analyzed during the initial analysis could be ignored in subsequent analyses.
This alignment only occurs before the initial analysis. If a new technology is detected in a subsequent New scan, the file extension lists for that technology are not populated in the same way:
- the first analysis that includes the new technology will process all the files supported by the installed discoverers
- any subsequent analysis will only process the files matching the extensions listed in the analysis configuration options, therefore some files that were analyzed previously will be ignored
For example, if you onboard an application containing only JEE source code and run an analysis, then run a New scan which adds Mainframe source code containing .ctl files, these .ctl files will be analyzed in the next analysis, but they will be ignored in all analyses after that. To avoid this, add the .ctl extension to the JCL file extension list in the analysis configuration options before you run the next analysis.
Also see the child pages listed below.