Introduction to analysis configuration options Include Page |
---|
| Introduction to analysis configuration options |
---|
| Introduction to analysis configuration options |
---|
|
Auto-configuration validationTechnology / Application levelUsing the Technology level or Application level options, validate the settings for ASP packages. Make any update as required. These settings apply to the Technology or Application as a whole (i.e. all Analysis Units): 

Analysis Unit levelTo inspect the auto-generated analysis configuration, you should review the settings in each Analysis Unit - they can be accessed through the Application editor: 
Technology optionsThe available options for configuring an analysis are described below. Note that some options are not available at specific levels (Technology/Application/Analysis Unit): Source SettingsThis tab shows the location of each type of source code in the ASP Analysis Unit - this is determined automatically by the CAST Delivery Manager Tool. You should, however, review the configuration and make any changes you need: 
Project path | The file based location of the corresponding project. This field is read-only. When the field contains User defined, this indicates that the Analysis Unit has been defined manually instead of automatically following the use of the CAST Delivery Manager Tool. | Application Root Path | Indicates the folder that is defined as the root folder for the Analysis Unit for analysis purposes. The Application Root Path is the path to the folder that contains WEB-INF directory. If this Analysis Unit is automatically defined, then this field will already be populated. You can choose a different source code location (use Browse) - or use the Reset button to re-populate the field with the information from the parent Application. |
Web Server Web Server File Extensions | This section displays a list of the file extensions that are included in the current file filter for your source code analysis. Only files that match these file extensions will be included in the analysis. | Also use Application Root Path for Web Server Files | If you select this option, the Application Root Path defined in the General tab will be used as a source for the web server files. If you wish to add additional source files use the option described below. | Files | |
Web Client Web Client File Extensions | This section displays a list of the file extensions that are included in the current file filter for your source code analysis. Only files that match these file extensions will be included in the analysis. | Also use Application Root Path for Web Client Files | If you select this option, the Application Root Path defined in the General tab will be used as a source for the web client files. If you wish to add additional source files use the option described below. | Files | |
AnalysisThe settings in this tab govern how the source code is handled by the analyzer: Click to enlarge 
Default Source Options/File Extensions - only visible at Technology and Application level. Web Server File Extensions | Use this option to specify the file extensions that will be considered as Web Server files for analysis purposes (typically .ASP files) | Web Server File Extensions | Use this option to specify the file extensions that will be considered as Web Client files for analysis purposes (typically .html files) |
Default Scripting Default Scripting Language for the client side / Default Scripting Language for the server side | These option enables you to select the Default Scripting Language for your client-side and server-side files. Use the drop down list box to choose between: It is possible to identify the default client scripting language by finding a ASP or HTML file with a SCRIPT tag that does not have a language definition (do a search for "<SCRIPT>") and examine the language to determine if it is JavaScript or VBScript. For an application that mixes both languages, you will need to find a file with <SCRIPT> tags that DO NOT have a language specified and <SCRIPT> tags that DO have a language specified. You then need to select the language NOT specified in the <SCRIPT> tag as the default language. |
Include Page |
---|
| Text replacement |
---|
| Text replacement |
---|
|
ProductionClick to enlarge 
The Production tab is only visible at Technology and Application level. Data to generate - Parsing options Add called files to selected files list | Selecting this option will automatically add any files to the list of files selected for analysis that are called by files that you have already selected. | Add included files to selected files list | Selecting this option will add any files to the analysis list that are included in files that you have already selected. | Maximal Complexity | This option enables you to manually enter a percentage which will refer to the m complexity of the analysis process.- A complexity percentage of 100 (default) corresponds to a maximum of 10,000 function analyses (function * context) for a given file.
- A complexity percentage of 70 corresponds to a maximum of 7,000 function analyses (function * context) for a given file.
- A complexity percentage of 0 corresponds to an unlimited analysis of all the called functions.
If the maximum number of function analyses is reached, this will be logged. No Format |
---|
File analysis too complex. Next function calls will not be followed by a function analysis if the function has already been analyzed |
When the limit is reached, links to the function will be created correctly, but links from the function will not be created. You should alter the complexity percentage if your analyses are taking a long time to complete with the default setting of 100%. Changing the percentage to a lower figure will reduce the number of function analyses for a given file, thus improving performance. Remember though that doing will cause some links not to be created. |
|