On this page:
The CAST AI Admin is responsible for validating the source code delivered by the Delivery Manager(s) before accepting the delivery and proceeding with the configuration and execution of the analysis.
Typically issues at this stage are due to missing files and other deficiencies that result in an incomplete delivery. Resolution includes either a request for the missing component or the decision (wherever possible) to proceed with a redefined analysis boundary that excludes the undelivered components.
There are significant differences in the delivery validation depending on whether the validation pertains to a first time delivery during an application on-boarding or to delivery of a new version of the source code of an application previously on-boarded.
Where you are undertaking an application reanalysis, the delivery validation can often be limited to inspecting the CAST Delivery Manager Tool delivery log (see Reviewing the Delivery Log below). Examining the delta between two deliveries can help to assess if the changes are expected or are "reasonable" and therefore do not require a partial or full re-qualification and a new on-boarding of the application.
During the an initial application on-boarding, the review and acceptance of the source code delivery requires a more in depth assessment against what is discovered during the Qualification step.
This step involves reviewing the package log and any warnings that may be displayed. You can access the log in one of two ways:
Launching the CAST Delivery Manager Tool from the CAST Management Studio (Application editor) and inspecting the content of EACH package that has been delivered:
Launch the DMT using the above icon
Accessing the Log Viewer from the Package Content tab in the DMT
|Note that when running the CAST Delivery Manager Tool direct from the CAST Management Studio, the Java Heap Space memory threshold is set to 640 MB. If you are experiencing out of memory issues, then CAST highly recommends launching the CAST Delivery Manager Tool from the CAST AIC Portal ensuring that a 64bit JRE is being used.|
You can also use the DMT (Package Content tab) to view information about the projects that have been identified, the alerts that have been generated and the files that have been found:
Please see the CAST Delivery Manager Tool help (tap F1 in any location in the DMT to open the help) for more information about the information provided in the Package Content tab.
|The Delivery Manager Tool displays "delta" information when (Added/Removed columns) when you are delivering a new Version of the same Application.|
During an application on-boarding, the validation steps include cross validation of the Package Content report with information gathered during the pre-analysis step via the Qualification process and then reviewing any warning, error or alert raised.
It is important to note here that the DMT, in the current version, only provides a simple list of what has been extracted and included in the package. The inspection of this list may trigger the need for further analysis of the delivered source code and in some cases the need for pre-processing it before analysis (see Qualification).
The CAST Delivery Manager Tool offers two reporting functions: discovered files and a delivery report. You can use these functions once the packaging action is complete:
This option will generate an XML based report listing all items in the delivery, for example:
The report will open with the default application assigned to open XML files. The report will only contain information once the Package action has been run. Full details of what is provided in the Delivery Report are shown below:
When any issue is detected and/or unresolved questions are raised, the analysis process should be halted as the delivery cannot be accepted until these issues are fully resolved. The CAST AI Admin should therefore reject the delivery in the CAST Management Studio:
When the delivery is rejected, the CAST Management Studio does not automatically notify the Delivery Manager(s) of the rejection. Moreover there is no justification why this has occurred. Thus while the Delivery Manager can discover that a prior delivery has been rejected by reopening the DMT and noting the change in status of the prior delivery, they will not know why this has been rejected by the CAST AI Admin.
CAST recommends that when a delivery is rejected, the CAST AI Admin notifies (via email) the Delivery Manager of the rejection, providing a reason and possible remediation actions that may be required before a a new delivery.
Accepting the delivery is a two step process that results in the transfer and de-archiving of the delivered package(s) into the Deployment folder (see Window > Preferences > Platform Settings in the CAST Management Studio):
By default the Deployment Path points to the Deployment folder configured in the CAST Management Studio (Window > Preferences > Platform Settings), however you are free to to choose any location you require. CAST recommends using the default suggestion to ease future source code deployment. Please also refer to Set-up a file repository for your analysis data for more information.
Note that if, for any reason, the delivery is rejected following the deployment of the delivered package, the folders created as a result of the package deployment will not be removed from the Deployment folder until a new delivery of the application is completed.