On this page:

Target audience:

CAST AI Administrator

Summary: this section explains how to initialize the CAST Management Studio  - i.e. configure a CAST license key and define the source code Delivery and Deployment folders.

Introduction

Once the CAST schemas have been successfully installed (see previous step: Install CAST schemas) you now need to initialize some settings that are required by the CAST Management Studio. You can do this in two ways:

Via the CAST Management Studio GUI

When using this method, you must repeat the instructions for each Management Service schema that you have installed. The CAST Management Studio should be run from the CAST Administration workstation installed in Step 1: Install CAST AIP components.

Launch the CAST Management Studio

The CAST Management Studio can be launched as follows:

Please note that only one single instance of the CAST Management Studio should be used with one single Management Service. CAST does not recommend using multiple instances of the CAST Management Studio (on different workstations for example) to interact with the same Management Service. Data corruption is highly likely and cannot be repaired.

Using the Startup wizard to define the license key and delivery/deployment folders

The Startup wizard is only launched the very first time you launch the CAST Management Studio. In subsequent launches, the wizard will not be displayed.

The Startup wizard guides you through the configuration of various mandatory settings. These settings are vital to the CAST Management Studio and without them you cannot use CAST AIP:

Source Code Delivery Folder

A central location for storing successive and compressed versions of an application's source code as packaged by the Delivery Manager(s).

You must define the EXACT SAME Delivery Folder location as defined when you installed the CAST AIC Portal (see Installing and configuring the CAST AIC Portal). You can find out more information about the configuration of the Delivery folders in Where should the Delivery folder be located.
Source Code Deployment FolderA storage location that is only accessed by the CAST Management Studio, as such CAST recommends defining a "local" folder on the CAST Administration workstation (i.e. the machine on which the CAST Management Studio is installed).
Both folders 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).
Default FoldersThis option will create a folder tree in the root of the selected drive as follows:
  • DRIVE:\CASTMS\Delivery
  • DRIVE:\CASTMS\Deploy

In addition, the Log Root Directory, Large intermediate storage area and Large temporary storage area options (see Window > Preferences > CAST General in the CAST Management Studio) will also be configured to the DRIVE:\CASTMS location.

If you select this option then you must ensure that the CAST AIC Portal is also defined to use this auto-defined Delivery folder (i.e.: DRIVE:\CASTMS\Delivery), which may not be appropriate.
Custom Folders

This option allows you to choose the location for the Source Code Delivery Folder and Source Code Deployment Folder yourself. This is useful if the default location of DRIVE:\CASTMS is not appropriate - i.e. the folder you want to define is not on the local machine.

The location must already exist on the drive before you input it. You can manually enter the path to the folder by hand or use the Browse buttons to select the location.

Please note that you can use the following syntax:

  • D:\CAST\DELIVERY (folder local to the host machine) - Please use this syntax when the CAST AIC Portal and the CAST Management Studio are located on the SAME machine. In this situation, always enter an absolute path to the local drive containing the Delivery folder (for example D:\ CAST\DELIVERY). Please DO NOT use a mapped drive path (created using the Windows GUI or the subst Windows command) that points to a folder on the local machine or to a remote network share - doing so can cause an error that will prevent the CAST AIC Portal/CAST Management Studio from functioning.
  • \\HOST\CAST\DELIVERY (folder on a remote network share) - note that forward slashes will also function. Please use this syntax only when the CAST AIC Portal and the CAST Management Studio are located on different machines. Note that forward slashes will also function.

Note:

  • Any user that wishes to interact with the Delivery folder from the CAST Management Studio (for example, when Accepting a delivery, using the Set as current version option or when running the CAST Delivery Manager Tool from the CAST Management Studio) will require read/write access permissions on the Delivery folder
  • You cannot choose the same location for each folder -
  • You must ensure that:
    • a different location is used for each folder (i.e. the Delivery folder should not be a sub-folder of the Deployment folder or vice-versa)
    • each folder is completely separate from the location used to store your source code - i.e. errors will arise if you configure the Delivery and Deployment folders to be located in sub-folders or a source code storage location
  • If you select this option, the Log Root Directory, Large intermediate storage area and Large temporary storage area options will use default locations (see Window > Preferences > CAST General in the CAST Management Studio).

Via the CAST Management Studio CLI

When using this method, you must repeat the instructions for each Management Service schema that you have installed - however, you can combine the instructions for each Management Service schema in one batch file and then run that batch file to configure all settings on one go.

To use this method, CAST recommends creating an empty batch file and placing the required commands in the batch file - the batch file can then be executed simply by double clicking it. To execute the action via the command line, you must specify the CAST-MS-CLI.exe executable (rather than the CAST-MS.exe executable). The syntax required is as follows:

CAST-MS-CLI.exe ConfigurePlatformPreferences -connectionProfile "<profile_name>" -licenseKey "<license_key>" -sourceDeliveryFolder "<path_to_delivery_folder>" -sourceDeploymentFolder "<path_to_deployment_folder"
OptionDescription

-connectionProfile

Specifies the name of connection profile to use to connect to the chosen CAST Management Service schema. You can obtain this information from the Connection Profile dialog box in the CAST Management Studio - note that Connection Profiles can include white space, in which case, please ensure that you surround the name with quote marks:

During a combined installation process (simultaneous installation of all CAST databases - Analysis/Dashboard/Management/Measurement Services, see Install CAST schemas) CAST Server Manager will automatically create a connection profile or profiles to the Management Service(s) (<prefix>_MNGT) you have installed. If you did not install the CAST schemas using a combined install option, then no connection profile will be available and you will need to create one by clicking the  button and defining the details of EACH Management Service schema (<prefix>_MNGT) that requires initialization.

-licenseKey

Enter the license key provided to you by CAST.

-sourceDeliveryFolder

Enter the location for the Source Code Delivery Folder and Source Code Deployment Folder. Please see the section above in the table entitled "Custom folders" for more information about the path syntax that can be used.

-sourceDeploymentFolder

Output codes

The CLI will return two output codes:

Logging

By default (if no logging option is used in the CLI), the CLI will use the following location to store the log file relating to this process:

%TEMP%\CAST\CAST\<version_number>\CAST-MS<number>.log.txt

You can override the default log location using the following syntax enclosing the string in double quotes if it contains white space. The specified folder does not need to exist already:

-logRootPath <string>

Example

The following example updates one Management Service schema with a license key, a Delivery folder path, a Deployment folder path and includes a log file location:

CAST-MS-CLI.exe ConfigurePlatformPreferences -connectionProfile "v800_8348_mngt on CastStorageService _ NEFYN:2280" -licenseKey "xxxxx" -sourceDeliveryFolder "C:\CAST\Delivery" -sourceDeploymentFolder "C:\CAST\Deploy" -logRootPath "C:\CAST\Log"

Notes

CAST-MS-CLI.exe ConfigurePlatformPreferences -connectionProfile "<profile>" -licenseKey "<xxxxx>"

Importing the Assessment Model for a CAST AIP Extension (optional)

If you have installed a CAST AIP Extension while installing the CAST AIP schemas, you now need to import the Assessment Model to ensure that any Quality Rules delivered with your CAST AIP Extension are activated when you run an analysis/generate a snapshot: