Application onboarding for CAST Imaging - prerequisites on Documentation - V2

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

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

Introduction

When adding a new version to analyze an Application that includes JEE based source code and this source code does not contain a .pom or .project file, C onsole will behave as follows:

Info

Behaviour in Console ≥ 2.3

Console will automatically install the

JEE File Discoverer whenever a .java file is encountered in your delivered source code. This extension will ensure that the required Analysis Units are created for your source code and that an analysis can proceed without issue.

Configuring source code delivery for Maven for CAST Imaging

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

Introduction

When adding a new version to analyze an Application that includes Maven based****source code, you have several choices with regard to specifying where the required Maven repositories are located. The location of the repository is crucial to ensure that any associated JAR files can be automatically discovered and that POM dependencies can also be located. You can do as follows:

You can include the Maven repository when you deliver the source code (i.e. in the ZIP or in the designated source code folder). Place the contents of the Maven repository (using the same file structure) at the root of the ZIP, for example:

D:\temp
	|-----JEE-Java
	|-----MavenRepo
	|-----OtherTechno2

You can define local Maven repositories for a single Application
You can define remote HTTP/S Maven repositories for a single Application
You can define local Maven repositories for all Nodes/Applications
You can define remote HTTP/S Maven repositories for all Nodes/Applications

Console will also use the above order to prioritise the various repositories. In other words, if you include a repository in the ZIP or in the designated source code folder this will be used instead of any local or remote repositories that have been defined at global or Application level.

Configuring source code delivery for .NET for CAST Imaging

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

Prepare the application source code

AIP Console expects the application source code to be delivered either via a ZIP file or via a **source code located in a folder**configured in AIP Console. Whichever option you chose, you should include in the ZIP/source code folder all of your .NET application source code. CAST highly recommends placing all the relevant files in a folder and using sub-folders where necessary. You can deliver other technologies at the same time (for example, database DDL). If you are using a ZIP/archive file, zip the folders in the “temp” folder as shown in the image below - but do not zip the “temp” folder itself, nor create any intermediary folders: