Summary: This section describes how to prepare and deliver the source code of your SAP ABAP application.
Information about discovery
Discovery is a process that is actioned during the delivery process. CAST will attempt to automatically identify "projects" within your application using a set of predefined rules. Discoverers are currently embedded in AIP Core:
You should read the relevant documentation for each discoverer (provided in the link above) to understand how the source code will be handled.
Source code delivery using CAST Console
CAST Console expects either a ZIP/archive file or source code located in a folder configured in CAST Console. You should include in the ZIP/source code folder all extracted SAP/ABAP source code:
- results of a com.castsoftware.aip.extractor.sap extraction
- directly from an abapGit repository (supported for analysis with the SAP ABAP Analyzer ≥ 1.0.8-funcrel) - see Prepare and deliver the source code in SAP ABAP - Prepare and deliver the source code for details about this).
CAST highly recommends placing the files in a folder dedicated to SAP/ABAP. If you are using a ZIP/archive file, zip the folders in the "temp" folder - but do not zip the "temp" folder itself, nor create any intermediary folders:
D:\temp |-----SAP/ABAP |-----OtherTechno1 |-----OtherTechno2
.SQLTABLESIZE files
XXL table rules (see XXL and XXS tables rules enablement) are performance related 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 goal is to use table size from production systems because development / integration systems may not feature really large tables and would not help detect real threat on application performance levels.
Note that:
- The com.castsoftware.aip.extractor.sap will automatically generate the .SQLTABLESIZE file when you extract the SAP/ABAP source code.
- You will need to manually create this file if you are packaging code directly from an abapGit repository.
You should ensure that you deliver the .SQLTABLESIZE file with your extracted SAP table code.