On this page:

Target audience:

CAST AI Administrators

Summary: this page provides information about where the Delivery folder should be located. As mentioned in Source code delivery - an introduction, this folder is crucial to the functioning of the CAST Management Studio and the CAST AIC Portal and therefore it is vital that this folder is defined correctly.

What is the Delivery folder?

The Delivery folder is first and foremost a location used by the CAST AIC Portal for storing successive and compressed versions of an application's source code as packaged by the Delivery Manager(s) using the CAST Delivery Manager Tool. In addition, the CAST Management Studio also requires access to this same Delivery folder so that source code packaged by the Delivery Manager(s) can be acquired and then analyzed.

As such, the choice of location for the Delivery folder is extremely important and may impact where the CAST AIC Portal is installed.

Where should the Delivery folder be located?

To answer this question you need to take into account where the CAST Management Studio and the CAST AIC Portal are to be installed, because both components require access to the same Delivery folder. The following addresses all scenarios:

The Delivery folder must be capable of receiving large amounts of data (i.e. source code packaged by the CAST Delivery Manager Tool and any associated configuration files).

You want to deploy the CAST AIC Portal and CAST Management Studio on the same machine

To deploy the CAST AIC Portal and the CAST Management Studio on the same machine (in small deployment environments), then the Delivery folder can also be defined on the same machine (a "local" folder to both the CAST AIC Portal and the CAST Management Studio):

You want to deploy the CAST AIC Portal and the CAST Management Studio on different machines

To deploy the CAST AIC Portal and the CAST Management Studio on different machines, you must ensure that the Delivery folder is available to both - there are three options:

Please take into account the following note IF the Delivery folder is remote to the machine on which the Application Server is running:

  • In a Windows deployment, the Windows user used to run the Application Server must have read/write access permissions on the Delivery folder

A folder mounted on a remote file server or NAS and shared over the network

A folder "local" to the CAST Management Studio that can be shared and accessed by the CAST AIC Portal

A folder "local" to the CAST AIC Portal that can be shared and accessed by the CAST Management Studio

How many Delivery folders do I need?

You must configure a unique Delivery folder for each CAST AIC Portal that you will deploy and in most standard cases you will only need to deploy one single CAST AIC Portal - therefore one Delivery folder and one CAST AIC Portal. You can deliver source code for multiple Applications in to one Delivery folder/CAST AIC Portal combination.

How is the Delivery folder defined?

The Delivery folder is defined as follows:

ComponentConfiguration action
CAST AIC PortalThe Delivery folder is defined in a web.xml file that is configured as part of Installing and configuring the CAST AIC Portal.
CAST Management StudioThe Delivery folder is defined in a Startup Wizard the first time you launch the CAST Management Studio - as described in Initialize the platform preferences in CAST Management Studio
CAST Update ToolWhen upgrading from a previous version of CAST, the CAST Update Tool (CUT) requires the location of the Delivery folder.
Above all, please remember that the Delivery folder is one unique folder that is accessed by two components of CAST AIP; the CAST Management Studio and the CAST AIC Portal. Therefore the SAME folder must be defined in each component.