Application onboarding without Fast Scan - Step-by-step onboarding on Documentation - V2

Application onboarding without Fast Scan - Step-by-step onboarding - Add a new version and deliver source code

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

In the Console, source code for a given Application is organised into v****ersions - the idea being that you can create new Versions when the Application’s source code changes and you want to measure these changes. When working with a new Application, an initial version first needs to be created and source code delivered so that it can be analyzed. This page describes how to do this.

Info

Analysis should be disabled

Application onboarding without Fast Scan - Step-by-step onboarding - Validate and accept the version

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

When the source code has been delivered (see Application onboarding without Fast Scan - Step-by-step onboarding - Add a new version and deliver source code) it should be validatedbefore it is accepted for analysis. This section explains how to achieve this.

Typically issues at this stage are due to missing files and other deficiencies that result in an incomplete source code 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.

Application onboarding without Fast Scan - Step-by-step onboarding - Review analysis configuration and execution

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The source code delivery process streamlines the analysis set-up by suggesting a default analysis configuration when the delivery is validated and accepted. In the vast majority of cases, this default analysis configuration will produce coherent analysis results, however CAST recommends that the default configuration is reviewed before running the analysis. This review process contains several steps, each listed below.

Review technology specific settings as well as Analysis Units
Review dependency configuration
Review module configuration
Review Assessment Model

Review technology specific settings

Move to the Console screen if you are not already there:

Application onboarding without Fast Scan - Step-by-step onboarding - Run the analysis

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

You are now ready to run the analysis (and save the results) but not quite ready to generate a snapshot and upload results for the CAST Management (Health) Dashboard or CAST Imaging. Running the analysis and saving the results for the first time still requires you to validate the analysis log to ensure the configuration is accurate. We will focus here on the options available and best practices to follow when executing an initial application analysis.

Application onboarding without Fast Scan - Step-by-step onboarding - Validate the initial analysis

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

This step should always be executed as part of the initial analysis of an application performed during the on-boarding. Once the analysis is complete, the following needs to be checked:

the generated log files need to be reviewed to verify that no errors or warnings which may impact the quality of the results have been produced. For each of the technologies supported by CAST, the log manager will produce a set of statistics to verify the analysis and compare this to the previous analysis.
the Analysis boundary to ensure that what has been analyzed and saved into the Analysis Services schemas as objects and links is consistent with the intent and scope of the analysis configuration.
the quality of the analysis.
the configuration of Modules (important for Dashboards and CAST Imaging).

Validate analysis based on log messages

To check the logs, you can click the View log option in the Job Progress panel:

Application onboarding without Fast Scan - Step-by-step onboarding - Validate Dynamic Links

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Ensuring the correct discovery of transactions is a multi-step process that may be complex and time consuming for applications that are not supported out-of-the-box. At the core of CAST transaction discovery algorithm is the understanding of the links between objects discovered during the source code analysis of the target application.

CAST automatically sets up default Dependency Rules (see Validate dependency configuration) when the source code is delivered and set as the current version: the source code objects are scanned for references to other objects and links are created where appropriate. Not all links generated in this fashion are valid and their validation by the AIP Super Operator is therefore required.

Application onboarding without Fast Scan - Step-by-step onboarding - Re-analyze and publish to CAST Imaging

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The final step is to re-analyze your Application if necessary (only required if you made any configuration changes in previous steps), and then publish the data in CAST Imaging.

Process

To re-analyze and publish to CAST Imaging, move to the AIP Console screen if you are not already there:

Locate the Application and click the Publish to CAST Imagingoption as highlighted below:

Click to enlarge

In the subsequent popup, before clicking Run, ensure:

Application onboarding without Fast Scan - Step-by-step onboarding - Snapshot generation and validation - optional

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

The final step is to generate your Snapshot, which enables you to create data that can be exploited primarily in the Health and Engineering Dashboards.

Generate the snapshot

To generate a snapshot, move to the Console screen if you are not already there:

Locate the Application and click the Run analysis option as highlighted below:

In the subsequent popup, before clicking Proceed, ensure:

that the Application Version is set to the version you need. By default, the accepted Version will be set as the version to generate a snapshot for.
that you:
- disable Run Analysis (you should already have run an analysis at this stage - see **Application onboarding without Fast Scan - Step-by-step onboarding - Validate the initial analysis**therefore to save valuable time, there is no need to run it again)
- enable Take a snapshot
- disable Publish to CAST Health Dashboard (snapshot should be validated before being published in the Health Dashboard)
that you define the snapshot name (default syntax offered will be Snapshot-YYYY-MM-DDTHH:MM:SS.sss) and capture date (DD/MM/YYYY HH:MM) - note that snapshot names MUST be unique.
choose whether you want to run an application backup before starting the process (some additional processing time is required while the backup completes). Backups are stored in the following location on the relevant AIP Node and can be managed in Administration Center - Applications - Application Details: %PROGRAMDATA%\AipConsole\AipNode\backup\<application_name>\YYYYMMDDHHMM.zip