Prerequisites - Application onboarding

Before beginning the application onboarding process, ensure the following prerequisites are completed:

Determine extension strategy

Out-of-the-box, Console contains very few restrictions or settings with regard to extensions, i.e. the following types of extensions can be installed automatically (by Console) or manually (by an Application Owner):

Official CAST Extensions and those from CAST Labs or the User Community (see Contributor types)
LTS and Funcrel extensions (see Release types)

While this provides flexibility, it can sometimes be problematic. To counter this, Console provides a set of Extension Strategy settings that can be used to control the extensions that can be installed both automatically and manually in the integrated GUI and it is highly recommended that this strategy is implemented before any Versions are created.

See Determine Extension strategy - v. 2.x or Determine Extension Strategy - v. 1.x for more information.

Configure upload to CAST Imaging

To upload results directly to CAST Imaging, you must configure the upload settings. See Administration Center - Settings - Imaging Settings. When using the onboarding with Fast Scan workflow in Console ≤ 2.7, it is mandatory to configure an upload to CAST Imaging otherwise the ability to perform an analysis will be disabled. This requirement has been removed in ≥ 2.8.

If you are using AIP Core for CAST Imaging (https://extend.castsoftware.com/#/extension?id=com.castsoftware.aipimaging&version=latest) - a dedicated AIP Core specifically for those that are not using CAST Dashboards - then the CAST Imaging integration will already be configured (this is done as part of the installation process).

Configure .NET / Maven / JEE source code options

When onboarding an Application that includes .NET based source code or Maven based source code, you must tell Console where to find the .NET framework (system assemblies) / JAR files. The location of these items is crucial to ensure that the analysis completes successfully. See:

In addition, if your JEE source code does not have .pom or .project files, then you can configure Console to correctly understand this source code. See:

Configuring source code delivery for JEE without .pom file or .project file

Prepare source code

You may need to run an extractor to obtain the source code in a format that CAST can interpret. See the following for more information:

Source code can be delivered in two ways:

ZIP file	Source code can be prepared in a ZIP (or tar.gz) file.
Source code folder	You can alternatively place source code in a predefined folder which your Node can access. See Administration Center - Settings - Source Folder Location for more details about how to configure this.

CAST recommends organizing different source code into dedicated folders. For example:

ZIP
	|
	----Java source code folder
	|
	----SQL source code folder
		|
		----app1.sql
		----app2.sql

You should also consult the specific documentation for your technology type, see CAST AIP Technologies Documentation for information about "qualifying" your source code (i.e. specific things you may need to do).