Page tree
Skip to end of metadata
Go to start of metadata


Summary: During "normal" re-analysis of an application this entire step should be skipped unless as part of the delivery validation significant differences in the delivered source code trigger any new technical qualification of the application. In case of re-analysis, the approach is often reactive and warnings and/or errors reported in the analysis log are what trigger the critical review and fine tuning of the analysis configuration.

The DMT based delivery process streamlines the analysis set-up by suggesting a default analysis configuration. There are two scenarios to consider: 

  1. When project files are present, the DMT can automatically generate an analysis configuration and the corresponding Analysis Unit. In this situation, when no errors/warnings are reported by the DMT during the packaging step, only minor fine tuning and validation of the analysis settings are to be expected.
  2. If project files are missing or in a format not supported by the DMT (see specific for each technology in the DMT help, topic Discovery - how does it work?), the CAST AI Admin will need to manually build the Analysis Unit and related analysis settings.

For some known situations, addressing broken links requires applying predefined enrichment packages and rerunning the analysis.

Scenario 1 - validation of auto created Analysis Units

When project files are present, the DMT can automatically generate an analysis configuration and the corresponding Analysis Unit. The validation of the analysis configuration may include the following tasks: 

  • Review Technology and Dependency Settings - Review Analysis Units and the configuration of the application specific technology stacks.
  • Run the analysis in test mode and inspect analysis log  -  Running the analysis leveraging the proposed configuration is best way to confirm the analysis setting, Configuration changes should be considered only to fix any error or warning reported in the analysis log* 
    *Additional changes in the recommended analysis configuration may be required in support of a Dynamic Links review or to overcome issues that result in missing transactions (see later subsequent sections).

If new problems arise in this step that require a new delivery, the CAST AI Admin can use the CAST Management Studio to reject the delivery, thus resetting the workflow to the source code delivery step.

In some unknown but rare circumstances, setting the delivered version as the current version will cause the creation of duplicated Analysis Units. If this occurs, further action will be blocked. This unstable state should not occur frequently. The first recommendation in this situation should be to restore a backup if available. The second option is to contact Support for advice. The third option is to remove the duplicated AUs.

Scenario 2 - manual creation of Analysis Units

If the DMT is not able to detect projects in your source code, then no corresponding Analysis Units will be created in the CAST Management Studio. The source is still delivered and deployed, but you will need to manually create the required Analysis Units yourself. This can occur, for example when your source code is a non-Microsoft C++ Application (there may also be other situations where this can occur).

To create your own Analysis Unit in the CAST Management Studio:

  • In the Application editor, click the Current Version tab
    • Select the Deployed package which has no corresponding Analysis Unit (1)
    • Click the + button to add a new Analysis Unit (2)
    • Select the type of Analysis Unit you want to create - this must correspond to source code of your technology type (3)

  • The selected Analysis Unit editor will then open enabling you to define the Analysis Unit. For example, here we are creating a C++ Analysis Unit:
    • In the Source Settings tab (1)
    • Click the Add Source Folder button (2)
    • Select the root source folder for your project (3). By default the CAST Management Studio will select the location of the deployed package in the Delivery folder:

  • Finally, make any other configuration changes you require in the Source Settings tab and the Analysis tab
  • Your Analysis Unit is now defined and you can continue with the validation process for any other auto generated Analysis Units as described in this guide.

Previous: 2.1.1. Validate and Accept the DeliveryNext: 2.2. Execute the Analysis

  • No labels