Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The CAST Management Studio can be launched as follows:
    • Either by selecting the CAST Management Studio shortcut location in the Windows Start menu (created when running the CAST Security setup)
    • Or by navigating to the CAST Security installation folder and double clicking the CAST-MS.exe application
  • The Database Connection Manager will then be displayed:

...

  • During a combined installation process (simultaneous installation of all CAST Security schemas - see Create CAST Security schemas), CAST Server Manager will automatically create a connection profile to the Management Service schema (<prefix>_MNGT) you have created. 
  • Select the connection profile in the list, and then click Connect.
  • The Startup Wizard will then be displayed.
Note
Please note that only one single instance of the CAST Management Studio should be used with one single Management Service schema. CAST does not recommend using multiple instances of the CAST Management Studio (on different workstations for example) to interact with the same Management Service schema. Data : data corruption is highly likely and cannot be repaired.

...

  • In order to function correctly, CAST Security requires various folders that are used to store source code, logs and temporary files. The location of each folder is particularly important, in particular, the CAST AIC Portal must also be able to access the Source Code Delivery Folder.
    • 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)
    • Source Code Deployment Folder - a location used exclusively by the CAST Management Studio to store the most recent version of the application's source code for analysis in uncompressed format
    • Logs folder - a location used to store logs of all interaction with the Analysis or Dashboard Services.
    • LISA (Large intermediate storage area) / LTSA (Large temporary storage area) - location to store temporary files generated during the analysis process
  • By default, the following paths listed in the table below will be preloaded into each field - you are free to leave the paths at their defaults or customize them as required:.
  • Make your choice and then click Finish to complete the Startup Wizard.
  • The CAST Management Studio will then be displayed.
OptionDefault PathsNotes
Source Delivery%SystemDrive%\CASTMS\Delivery
Note
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 from the CAST AIP documentation). You can find out more information about the configuration of the Delivery folders in Where should the Delivery folder be located (from the CAST AIP documentation).
  • If the CAST AIC Portal and the CAST Management Studio are deployed on the same workstation, then the folder can also be defined on the same machine (a "local" folder).
    • 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.
  • If the CAST AIC Portal and the CAST Management Studio are deployed on different workstations, then the folder must be available to both. You can use the following syntax: \\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. For example:
    • a network drive
    • 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
  • The CAST AIC Portal must be able to access the Delivery folder path
  • 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
Source Deployment%SystemDrive%\CASTMS\DeployA storage location that is only accessed by the CAST Management Studio, as such CAST recommends the use of a "local" folder on the CAST Administration workstation (i.e. the machine on which the CAST Management is installed).
Logs%PROGRAMDATA%\CAST\CAST\Log

Use this option to define a log directory in which to store logs of all interaction with the Analysis or Dashboard Services. Once defined, the following log files are generated:

  • one folder (named with a unique ID) per Application will be generated when you use the CAST Delivery Manager Tool, run an analysis or generate a snapshot. Its contents include the analysis logs and Delivery Manager Tool specific logs (such as Validation/Selection/Discovery):
  • a log file called "CAST_MainTask_SummaryLog_<date>.txt" will be generated when you interact with the Analysis/Dashboard Service (i.e. run an analysis or generate a snapshot)
  • a log file called "DssEngine.<date>.log.txt" will be generated when you generate a snapshot - this logs the snapshot generation process
  • a log file called "RunCSV-<date>.castlog" will be generated when you generate a snapshot - this logs the update of the CAST System Views

Notes

  • If this field is changed to blank, the Log Root Directory will default to:
    • %TEMP%\CAST\CAST\<version_number>
  • Changes made here will not affect the location of the specific CAST Management Studio log (CAST-MSXX.log.txt), which is displayed in the Log view window.
LISA%PROGRAMDATA%\CAST\CAST\CASTMS

This option enables you to define a location (i.e. a folder) on your local hard drive that can be designated for use by the CAST Management Studio to store miscellaneous files generated during the analysis process. These files will still exist once the analysis is complete.

Once a location is selected using the browse option, a sub-folder called LISA will automatically be created. Generated files will then be stored in the LISA folder.

Notes

  • If this field is left blank, the CAST temporary folder will be used, i.e.:
    • %TEMP%\CAST\CAST\<version_number>\LISA
  • This location is used more particularly in the J2EE and .NET technologies to store data generated when the User Input Data Flow Security Analysis feature is activated.
  • Note that the location must be capable of receiving a large amount of data (several hundred MB).
  • This folder stores miscellaneous files - it is similar in nature to a browser cache.
LTSA%PROGRAMDATA%\CAST\CAST\CASTMS

This option enables you to define a location (i.e. a folder) on your local hard drive that can be designated for use by the CAST Management Studio to store temporary files generated during the analysis process. These files will be removed once the analysis is complete.

Once a location is selected using the browse option, a sub-folder called LTSA will automatically be created. Generated files will then be stored in the LTSA folder.

Notes

  • If this field is left blank, the CAST temporary folder will be used, i.e.:
    • %TEMP%\CAST\CAST\<version_number>\LTSA
  • This folder stores temporary files - it is similar in nature to the Windows %TEMP% folder.
Info

Please note the following additional information:

  • The folders defined in the startup wizard are set on a "per Management Service schema basis". This means that the folders should be used only for the Management Service schema that you connect to. If you connect to a different Management Service schema, you will be required to set new folder locations - and these should NOT be set to the same location.
  • 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 of a source code storage location
  • For custom paths, you can use the following syntax:
    • D:\CAST\DELIVERY (folder local to the host machine) - always enter an absolute path. 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.
  • The default paths that are pre-populated into the fields are taken from the CASTGlobalSettings.ini file (a file located at the root of the CAST AIP installation folder - see Appendix - Modifying default CAST data storage locations from the CAST AIP documentation) - changing the location in the CASTGlobalSettings.ini file will not affect the settings defined in the GUI.

...

  • .

...

Via the CAST Management Studio CLI

...

  • Once the settings have been successfully initialized using the command line interface, opening the CAST Management Studio and connecting to the Management Service in question for the first time will NOT cause the Startup wizard to be displayed.
  • It is possible to use the CLI interface to update all settings EXCEPT -sourceDeliveryFolder and -sourceDeploymentFolder once they have already been set either via the Startup wizard or via the CLI.

...