Deployment considerations

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

Info

Summary: information to help you plan your CAST AIP for Dashboards installation.

Typical communication between CAST components

The following diagram shows the interaction between AIP Console and the main CAST Components. It also shows the flow from the source code delivery to the snapshot and Dashboard data consumption.

Click to enlarge

Info

*Analysis Node = Server on which the AIP Node service and AIP Core are installed.

Hardware sizing

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

Info

Note that:

hardware requirements depend on various factors related to the Application(s) you are analyzing and these must be considered:
- Number of lines of code (LOC)
- Number of objects after analysis
- Number of violations after analysis
- Technologies used
- Number of users accessing results
due to the different factors that need to be considered, it is difficult to make precise hardware recommendations, therefore what we provide in this page is indicative only. We provide these figures as a guide to the absolute minimum required to run AIP Console and all required components, and your own configuration will likely require better hardware.
using storage/disk with high IOPS values (i.e. SSD disks or SANs configured with SSD) will bring better performance. This is particularly true for servers hosting the CAST AIP/AIP Node and PostgreSQL components where faster storage will improve analysis performance.
installations of CAST AIP on servers with resources that are lower than the minimum required or that barely meet the minimum requirements will have the following limitations:
- analysis runtime and SQL operations will be sub-optimal
- you cannot run more than one application in parallel
- disk space can be quickly overloaded

On-premises

Multi-node (Large/Enterprise)

With AIP Console v. 2.x

Component

Software requirements

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

Info

Summary: information to help you plan your CAST AIP for Dashboards installation.

Typical architecture

2.x

Click to enlarge

Deployment modes

Before beginning the installation process, you should be aware of the various deployment methods available:

Release	Deployment mode	Deployment scenario	Details
2.x	Enterprise	Docker for Linux or Docker Desktop for Microsoft Windows	Enterprise mode using Docker is highly recommended wherever possible: This mode uses microservices architecture: all Console front-end services (authentication, UI, registration, Dashboards etc.) are provided either: as Docker containers or can be installed via Java JAR installers where Docker cannot be used When using Docker/Docker Desktop: the deployment of CAST Dashboards is entirely automatic and no manual configuration is required upgrades to new releases of Console is simple - pull/rebuild new images for the containers The Node service is provided as a separate Java JAR installer for installation on Microsoft Windows and can be installed on multiple hosts where AIP Core exists
	Enterprise	Single installer (exe) for Microsoft Windows only
	Enterprise	Java JAR installers (multiple)
	Standalone	Java JAR installer (single) for Microsoft Windows only	Standalone mode is targeted at deployments on Microsoft Windows on one single machine. The installer includes all required services in one single Java JAR installer:

Prerequisites on Documentation - V2

Deployment considerations

Typical communication between CAST components

Hardware sizing

On-premises

Multi-node (Large/Enterprise)

With AIP Console v. 2.x

Software requirements

Typical architecture

2.x

Deployment modes