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

A key pre-condition for a successful analysis is the qualification of the target application's technical attributes. This process relay on the application team gathering of key information and on a formalized review procedure. 

This qualification process is depicted here:  

The qualification process includes the following key tasks:

  • 1.1. Registering new domains and applications in the CAST AIC Portal - This step is performed by the application team to trigger the on-boarding and first time analysis of a new application with CAST AIP.
  • 1.2. Delivery Managers and other key participants - This step is performed when on-boarding a new application with CAST AIP (initial analysis). The expected outcome of this step is to identify and document all application team analysis stakeholders and participants including the subject matter expert who is responsible for the application's source code delivery, including database schema delivery or live connection configuration for development instances.
  • 1.3. Application Qualification - This step describes how the CAST AI Admin facilitates the collection and review of application metadata that will be determine if any technical limitations exist and if any potential workarounds can be implemented.  
  • 1.4. Deliver the application source code version - This step is performed by the application team with the support of the CAST Admin. It encompasses all tasks associated with the registration of the application within the CAST AIC Porta: the extraction, packaging and validation of the application source code to be analyzed and with the delivery of the version. It may include, if required, the configuration of exclusions (e.g. test code) performed via fine tuning the configuration of the CAST Delivery Manager Tool packages and the pre-processing of the extracted source code to comply with the delivery requirements (e.g. pre-processing and reorganizing source code, or deploying delivered SQL dump files to reconstruct a live DB2 participating server).

How these tasks are implemented will largely depend on the deployment framework and organization specific constraints.

Before committing to the current platform for the analysis of the target application source code make sure you review the supported platforms and languages in the Release Notes and compare this with the list of officially supported languages/technologies for previous releases.
  • No labels