On this page:

Target audience:

CAST AI Administrators

Delivery Managers and the Delivery Manager role

The single most important participant in the Delivery process is the Delivery Manager. This person or persons, will be responsible for delivering the source code of the Applications and participating databases for analysis. As the CAST Admin, you need to identify who your Delivery Managers are.

Before your designated Delivery Managers can actually deliver the source code for Application(s), you need to grant them the Delivery Manager role. This is achieved by:

When a user logs into the CAST AIC Portal, he/she will ONLY be able to see the Domains/Applications for which he/she has been granted the Delivery Manager role.

Note that CAST highly recommends that you read 1.1. Registering new domains and applications in the CAST AIC Portal which explains in more details about Domains and Applications and how to create them.

Assigning groups to domains

The notion of groups functions slightly differently according to the authentication method you are using for the CAST AIC Portal (see CAST AIC Portal - Configuring user authentication):

Authentication ModeBehaviour
Default Authentication

In order to gain the Delivery Manager role for a given Application, the user must be a member of a group that has been assigned to the Domain containing the Application in question. Users are assigned to groups using the application-security-default.xml configuration file (as explained in CAST AIC Portal - Configuring user authentication) - in the example below showing the addition of a user called "jhu", the user is assigned to a group named "DELIVERY_GROUP1":

<prop key="jhu">mypassword,enabled,DELIVERY_GROUP1</prop>
Active Directory with LDAP and Standard LDAP

In order to gain the Delivery Manager role for a given Application, the user must be a member of an Active Directory or LDAP group whose CN (Common Name) matches the name of the group that has been assigned to the domain containing the Application in question.

So, for example, you may wish to create a new Active Directory / LDAP group called "corp.company.delivery" and assign your internal user to that group on your Active Directory / LDAP server. In the CAST AIC Portal GUI, you then need to assign a group called "corp.company.delivery" to the to the domain containing the Application that the user needs to deliver.

Note that only a user with the Platform Administrator role can assign groups to domains.

Note that you can add multiple groups to one single domain (click the Add button again and enter a new group name) and you can add the same group to multiple domains.

Assigning an individual user to a domain

Rename or delete an existing Group/User that has been assigned to a domain


When a group/user is deleted from the domain, any users assigned to the group or individual users you have removed will no longer have the Delivery Manager role for the domain's Applications. If they have already used the CAST Delivery Manager Tool to deliver source code for the Application(s) in question prior to the group/user being deleted from the domain, when the users attempt to use the Deliver or Refresh actions in the CAST Delivery Manager Tool they will be prevented from doing so and the following message will be displayed:

Other key participants

Besides the Delivery Manager and Application Owner it is important for the CAST Admin to identify other key analysis participants and stakeholders and gather some initial details about the application target for analysis. This is a recommended best practice during the application on-boarding that will streamline the gathering of qualification information and the quicker resolution of any issue that may arise during the configuration of the analysis and the delivery of the results. This has not been automated with the CAST AIC Portal and may be implemented in different ways. Often this consists of a quick meeting/call between the CAST Admin and the Application Owners. 

Preconditions and assumptions

The application owner has already been briefed about the purpose and objectives of the analysis with CAST AIP during the application wave kick-off meeting*. S/He has an understanding of the overall process and expected outcome. 

*The application wave kick-off meeting and any briefing and communication about the organization of the analysis program and CAST AIP are responsibility of the organization's SQI officer.


Use this table to gather some basic information about the application that will be analyzed:

Application Name 
Application Owner & Contact information 
Typical Release Frequency 
Other Info - Application specific area of interest/ focus 

Consumer and Stakeholder

Name and contact info

Source Code Delivery Manager(s) 

Database Delivery Manager(s)


Application Architect

Application SME(s)   

Other stakeholders (project manager etc.)


Previous: 1.1. Registering new domains and applications in the CAST AIC Portal 
Next: 1.3. Application Qualification