Technology settings are organized as follows:
- Settings specific to the technology for the entire Application
- List of Analysis Units (a set of source code files to analyze) created for the Application
- Settings specific to each Analysis Unit (typically the settings are the same as at Application level) that allow you to make fine-grained configuration changes.
You should check that settings are as required and that at least one Analysis Unit exists for the specific technology.
Click to enlarge
Dependencies are configured at Application level for each technology and are configured between individual Analysis Units/groups of Analysis Units (dependencies between technologies are not available as is the case in the CAST Management Studio). You can find out more detailed information about how to ensure dependencies are set up correctly, in Advanced onboarding - review analysis configuration and execution for AIP Console.
For Oracle Forms and Reports, there are no Analysis Unit level settings available. You can however:
CAST Management Studio
Introduction to analysis configuration options
Some settings at Application and Analysis Unit level have a "Reset" option - using this will reset the option to the value set at the parent level:
Technology / Application level
Using the Technology level or Application level options, validate the settings for your packages. Make any update as required. These settings apply to the Technology or Application as a whole (i.e. all Analysis Units):
Analysis Unit level
To inspect the auto-generated analysis configuration, you should review the settings in each Analysis Unit - they can be accessed through the Application editor:
The available options for configuring an analysis are described below. Note that some options are not available at specific levels (Technology/Application/Analysis Unit):
This tab shows the location of each type of source code in the Analysis Unit - this is determined automatically by the CAST Delivery Manager Tool. You should, however, review the configuration and make any changes you need:
|Extraction path||The file based location of the parent .uaxdirectory file (resulting from the output of the CAST Oracle Forms Extractor). This field is read-only.|
|Table Sizes Folder|
XXL table Quality Rules are performance related Quality Rules that help detect incorrect or poorly performing SQL queries running on XXL tables. XXL tables can be defined as extremely large tables, containing a large amount of data. The threshold that determines when a table is considered to contain a large amount of data can be configured by the user using the Assessment Models editor in the CAST Management Studio (Contextual Parameters tab) - the default is 100,000.
In order to enable these XXL tables Quality Rules it is necessary to provide the analyzer with table row size information. This can be done using the Table Size Folder option.
See XXL and XXS tables rules enablement for more information.
The settings in this tab govern how the source code is handled by the analyzer - only available at Application and Technology level:
Click to enlarge
|Directory for Code Viewer files||If you would like to be able to view the source code of your Forms/Reports analyses in CAST Enlighten, the CAST Discovery Portal or the CAST Engineering Dashboard, then you need to configure this option: enter a full path to a local or network folder. During the analysis, the Forms analyzer will create the files in the selected folder necessary for source code to be viewed by the CAST applications listed above. A sub-folder will be created for each analysed Application that contains Forms/Reports Analysis Units.|
Note the following:
Click to enlarge
Dynamic Links Rules
See the CAST Management Studio help for more information about this global option.