The packages delivered through the DMT are automatically transformed into Analysis Units where project files exist. CAST AIP will automatically detect the type of source code and recommend the most appropriate analysis settings for each Analysis Unit, for example:
CAST's recommended best practice is to accept the suggested configuration and make any changes only retroactively to address analysis log warnings and/or errors. If the application is very big, complex or you have to make some manual changes to address unsupported conditions, you could run the Analysis in Test Mode (analysis results are not saved) and fix any issues iteratively.
For more details on auto configuration, current limitations and additional validations that should be performed by the CAST AI Admin see the following technology specific pages:
- .NET - Confirm analysis configuration
- ABAP - confirm analysis settings
- C and Cpp - Confirm analysis configuration
- J2EE - Confirm analysis configuration
- Mainframe - Confirm analysis configuration
This step involves checking that the dependencies settings are correct for your technologies. Dependencies are configured at Application level in the Dependencies tab.
The default rules are as follows:
- any "client" results depend on all "server" analysis results
- J2EE analysis results depend on Mainframe results
Discovered rules are derived from the CAST Delivery Manager Tool and function between Analysis Units. Custom rules can be created manually.
Where several client technologies (for instance Java and C/C++) or several database schemas exist, the CAST AI Admin must set the correct dependencies, overriding the default settings if necessary. The fine tuning of dependencies settings can be configured by rules in the following files (please see the CAST Management Studio help for more information about this):
|8.2.2 and above||CAST_INSTALL_FOLDER\configuration\parametrization\CustomExternalLinksRules.xml|
Links between objects will be submitted for review in the Dynamic Link Manager tool (DLM). The more accurate the configuration, the less manual work is required in the DLM.
Incorrect dependency settings may result in missing links - missing inter-technology dependencies - or in a large number of Dynamic Links - incorrect dependencies. This can have a knock on effect on Quality Rule results and on Transaction flow.
JEE dependency rules
If the CAST Delivery Manager Tool did not detect any inter-Analysis Unit dependencies (i.e. Discovered dependencies) then it will create a "global" default dependency between JEE and JEE. CAST highly recommends that this default rule is removed if the deployed package contains more than three Analysis Units. In addition, CAST highly recommends that you avoid creating a custom JEE > JEE rule if the deployed package contains more than three Analysis Units.
This global default rule can cause the creation of inaccurate links between objects which has a knock on effect on Quality Rule results and on Quality Rule results and on Transaction flow.