On this page:
CAST AI Administrators
|Summary: this page explains how to configure Domains, Applications and the Delivery Manager role to organize access to and register new Applications.|
In previous versions of CAST, the tactical step of initiating the analysis process and the delivery of source code for analysis was responsibility of the "AI Administrator" (Application Intelligence Administrator) at the AI Center. The source code delivery did not follow a strict process and there were no tools to enforce a specific delivery format. This resulted in the source code being delivered in different formats and packaged differently between successive versions. This led to inconsistencies between versions and "pollution" of the source code analysis results and metric data.
CAST has now introduced a method for initiating, managing and automating the delivery of source code for analysis that is tightly integrated into the existing AI Center processes. This method brings together previous options and processes that have been available to CAST users for some time (namely the Discovery process - in the CAST Management Studio - for source code identification) and provides a new standalone tool that is used to manage the delivery of source code.
This method is known as source code delivery automation and the tools that are used to achieve this are known as the CAST AIC Portal and the CAST Delivery Manager Tool (or DMT). The aim of this document is to help position these tools and explain how they are configured and used.
The CAST AIC Portal is a web application that is deployed on a(for example Apache Tomcat) in the local environment. It is designed to be accessed via a browser by the Delivery Manager(s) - when accessed, the CAST AIC Portal will "push" the CAST Delivery Manager Tool as a "local" installation on to the workstation of the Delivery Manager.
As such, multiple Delivery Managers can run the CAST Delivery Manager Tool on their own local machines and package only the source code they need to. Source code packaged by Delivery Managers is delivered to one central location (the Source Code Delivery Folder) managed by the CAST AIC Portal, which can then be retrieved by the AI Administrator using the CAST Management Studio (which is configured to retrieve the delivered source code from the central storage location managed by the CAST AIC Portal).
Note that the CAST AIC Portal contains a basic built in documentation that explains the main aspects of the Delivery process and how it works:
The CAST Delivery Manager Tool is a standalone application that entirely manages the discovery, selection, extraction and delivery of source code ready for analysis in the CAST Management Studio. It can be used in different scenarios and is designed to be flexible to accommodate most options. It is "pushed" by the CAST AIC Portal and is installed on the local workstation. It can be relaunched whenever required.
The Delivery Manager(s) is the person within the application team who is responsible for providing source code for analysis. The source code can be of different types including:
Regardless of the type of source code, the Delivery Manager(s) can use the CAST Delivery Manager Tool to package and deliver it to the CAST AIC Portal and then into the AI Center for analysis. There may be more than one Delivery Manager, for example when multiple technologies or distributed development teams are involved. The CAST AIC Portal supports and facilitates this distributed delivery model.
CAST recommends that each Application you need to onboard and analyze with CAST is configured to have sole use of a "triplet" of CAST schemas as follows:
Application 1 uses:
If you need to analyze any additional Applications, CAST recommends that for each additional Application you install a new additional "triplet" of CAST schemas:
Application 2 uses:
Onboarding multiple Applications in the same triplet of CAST schemas can cause inter-Applications links to be created and other potentially undesirable side-effects.
With regard to Measurement Services that are required for the CAST Application Analytics Dashboard, you can choose to:
|Please see Install CAST schemas and Installing and configuring the CAST Application Analytics Dashboard for more information.|
One example setup (when using the CAST Storage Service) would be to:
CAST recommends using one CAST AIC Portal to manage source code for all Applications that you need to analyze with CAST. However, the CAST AIC Portal is CAST AIP version aware and can only manage Applications that are being administered with the same release of CAST AIP (in other words you cannot mix Applications that are being managed on CAST AIP 8.0.x with Applications that are being managed on CAST AIP 8.1.x - for example).
|Please see Installing and configuring the CAST AIC Portal for more information.|
As explained in CAST AIC Portal - Configuring user authentication, the configuration of Domains, Applications and the Delivery Manager role is achieved using the CAST AIC Portal GUI. Only a user that is a member of a group that has been assigned the Platform Administrator role (see also CAST AIC Portal - Configuring user authentication) can configure Domains, Applications and the Delivery Manager role, therefore you must connect to the CAST AIC Portal with a user that has this role (for example the default "cast" user).
|Note that you can configure your Delivery Managers when creating the domain, however, this process is explained separately in 1.2. Delivery Managers and other key participants.|
Note that if you attempt to delete a domain that contains Applications, the following confirmation message will be displayed:
Clicking OK will remove the domain and all its attached Applications. Any instances of the CAST Delivery Manager Tool that refer to an Application that has been deleted will no longer function.
If you want to employ an automated solution to create the domain and assign users and groups to this domain as Delivery Managers, you can do so using a command line tool provided with CAST AIP. Please see Automating CAST AIC Portal Configuration tasks for more information.
|Note that only a user with the Platform Administrator role can configure Applications.|
Note that the Application Name field cannot contain any of the following characters: \ / : * ? " < > |
|When moving the Application to another domain, all users belonging to groups assigned to the other domain will gain Delivery Manager rights on the Application you move.|
Note that if an Application is deemed "invalid", it is displayed in the CAST AIC Portal in red:
The only option available is to delete the Application.
|An Application is generally considered to be invalid if it has been registered in the CAST AIC Portal but does not exist in the Delivery folder.|
If you want to employ an automated solution to create the Application, you can do so using a command line tool provided with CAST AIP. Please see Automating CAST AIC Portal Configuration tasks for more information.