CAST HIGHLIGHT - Discovery Step - Analyzer not detecting all the technologies

Analyzer is found to skip some technologies at the discovery step.

Action Plan with Workarounds

  1. Check whether the analyzer supports the technologies that are used CAST HIGHLIGHT - Analyzer - Technologies Frameworks and File extensions supported
  2. If the file count exceeds 10,000
    1. Use the CLI which is less processor intensive or
    2. It is recommended to split  the scan into several separate scans. Multiple scans (different folders), can be run, then output ZIPs for the same application can be uploaded . Results will be aggregated into a single application result.
    3. Is the code being analyzed on a network drive?  If so, please place it on a local drive for better performance.
    4. Make sure that your analysis machine is not running out of RAM or CPU resources;  otherwise, you may want to run on a machine with better resources.
  3. Check if the file size is in excess of the limit of 3 MB.( Refer page 9 in In the future the product will have an option to increase file size limit to the value the user will define. But it should be noted that very large files tend to make the analysis less stable due to memory consumption. To manually increase the default file size that is allowed to be scanned, please refer CAST HIGHLIGHT - Analyzer - How to Increase the file size limit set for analysis
  4. Check the file extensions supported for each programming language . If the files, in the scope for the scan do not use the extensions listed there is a good chance the analyzer will not be picking them.
    1. Rename the File extensions as appropriate based on the list, for them to be detected by the local agent. More details about renaming the extension for each technology can be found in                ( pages 35-38 in,
    2. If an extractor is used, check if the files provided by the extractor is of an extension that the Highlight analyzer can identify. For eg CAST database extractors produce .src extensions by default, but to make it recognizable by the Highlight analyzer it should be renamed
       into .sql. More details can be found at  CAST HIGHLIGHT - Analyzer - Discovery Step - Highlight is not recognizing files extracted using AIP extractor
    3. For file extensions such as .inc which is a  shared file extension between C/C++ and PHP analyzers, if C++ analyzer is not analyzing it, the configuration file can be modified to analyze it using the PHP analyzer. Please refer CAST HIGHLIGHT - Analyzer - Discovery Step - Wrong technology classification when compared with CAST AIP
    4. Highlight expects specific file names (e.g., pom.xml, package.json, package-lock.json). If dependencies are not declared in files in this naming convention, CAST Highlight doesn't extract this info.
  5. Check the best practices for each technology to know about how the analyzer excludes, categorizes separately certain files or where manual selection or deselection of files is required
  6. Check if any folder name in the path has characters other than English. For more details refer CAST HIGHLIGHT - Analyzer - Discovery Step - Files are not getting analyzed because of other than English characters in the path
  7. Check whether code is not accessible due to some permission issues or network accessibility issues.
  8. Check if any folder name in the path has characters other than English. Ensure that Path length is less than 256 characters and there are no special characters in the path. Move the repository to higher level if needed. Please refer CAST HIGHLIGHT - Analyzer - Discovery Step - Files in subdirectories are not analyzed
  9. Check whether the dependency files (e.g. pom.xml, build.gradle, package.json, .vcsproj, etc.) are there to detect frameworks and dependencies whose physical files are not part of the folder you're scanning. The list of the frameworks that HL support and is automatically detected can be found at .If you use a framework or a library which is not referenced by Highlight, it can still be manually added ( page 30 in
  10. Remove any files from the scan scope which provide no value for the analysis and may end up in increasing the code size and resulting in memory based performance issue.  eg generated code like *.t.ds, *.flow.js also build and deployment folders .git,.svn etc. Please refer CAST HIGHLIGHT - Local Agent - Discovery Step - Additional files that should be excluded from Analysis
  11. If you scan with the Local Agent (GUI), utilize .casthighlight file in the scan folder to make discovery faster for repeated analysis of the same folder. CAST HIGHLIGHT - Local Agent - How to make discovery faster for the further analysis of a same folder

NB:  All the COBOL files are not getting scanned because Highlight do not support JCL and copy books, To view the list of COBOL extensions supported please  refer  CAST HIGHLIGHT - Analyzer - COBOL - All the cobol files are not getting scaned in highlight scan


Related Articles

CAST HIGHLIGHT - Analyzer - Discovery Step - .sql Files not getting scanned - No error in log

CAST HIGHLIGHT - Analyzer - Discovery Step - Oracle package code with file extension .plb is being scanned as PL/I in Highlight Agent

CAST HIGHLIGHT - CLI - PLSQL and TSQL not detected when scanned with Command line but detected when scanned with the Agent

CAST HIGHLIGHT - Analyzer - Discovery Step - Framework - AngularJS framework was not fully detected

CAST HIGHLIGHT - Analyzer - Discovery Step - Framework - Does Highlight support basic frameworks associated with Java technology like STRUTS or SPRING etc.

CAST HIGHLIGHT - Analyzer - Discovery Step - Scan in Jenkins is failing with an error "Discovery child process failed with exit status 2"

CAST HIGHLIGHT - Agent - Hangs while scanning CS files





Have more questions? Submit a request


Powered by Zendesk