CAST Universal Analyzer Framework Component

This page will help you solve problems related to Universal Analyzer framework.

If you want to analyze a language not already supported by CAST, then you need to configure the Universal Analyzer to do so using the proprietary CAST Universal Analyzer Framework (a set of categories that describe a language and how to analyze that language).

For more information, refer to:

• For 8.3 - Official documentation -  Creating or modifying a custom extension using the CAST Universal Analyzer framework
• Information Guides > Information Guides by CAST AIP Component > CAST Universal Analyzer Framework
  

1.  Select the section you are interested in:
   
   • CAST Universal Analyser Framework - UA Package Assistant
   • CAST Universal Analyzer Framework - Extension consider files for analysis even through the files are not part of extension technology
   • CAST Universal Analyzer Framework - The profile for Universal Analyzer language XXX could not be found
2. If you encounter issues with this feature, then contact CAST Technical Support and provide the below relevant input to help CAST Support team investigate your problem or procure the required information.

 Relevant Input

• CAST Support Tool (CST) - alias Sherlock export with the following options: Export Logs, Export Configuration files, Export Computer Environment,Export CAST Bases
  
• Screenshot of the problem - For example, you have defined your metamodel correctly using the correct tags yet, you are not able to see the objects in the Enlighten. Then you need to provide the screenshot of the part of the metamodel to justify that you have used the correct tag as shown below -
• If the language you want to analyze includes embedded SQL (i.e. calls to server-side database objects), then you need to tell the Universal Analyzer which objects need to be searched for embedded SQL. This can be done by ensuring that each object that needs to be searched for embedded SQL inherits from the ESQLSearchable category.
  
• link of the official documentation showing where you picked the tag from