Before beginning the onboarding process, ensure the following prerequisites are completed:
|Determine extension strategy|
Out-of-the-box, AIP Console contains few restrictions or settings with regard to extensions, i.e. the following types of extensions can be installed automatically (by AIP Console) or manually (by an Application Owner or Analysis Manager (see Administration Center - Security - User Roles)):
While this provides flexibility for Application Owners or Analysis Managers, it can sometimes be problematic. To counter this, AIP 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. 1.x or for more information.
|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 the AIP 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 AIP Console to correctly understand this source code. See:
|Add a new application||Before you can being the onboarding process, a new Application must first be added into AIP Console.|
|Prepare source code|
Source code can be delivered in two ways:
CAST recommends organizing different source code into dedicated folders. For example:
|Access AIP Console||To access AIP Console, use the following URL (ensure you specify the correct server and port number): |