This article describes how to move the AIP Console deployment area from the default directory to a custom directory
Workaround or Action Plan
See definitive solution
The following steps were needed to move AIP Console deploy and other folders from a default C: installation drive to a custom D: drive location:
1. The starting point was that all applications had been 'logically' removed from the Console using the Console CLI with the following syntax (see here for more on the CLI documentation: https://doc.castsoftware.com/display/AIPCONSOLE/Delete+an+Application+via+CLI ):
deleteApplication.bat -apiHost "http://host:<port>" -appName "<application>" -keepData -token "<token>"
2. Updated aip-node-app.properties file to point to D (see here for related documentation: https://doc.castsoftware.com/display/AIPCONSOLE/Configure+AIP+Node+storage+folder+locations+-+optional)
# Storage folders location
3. Updated castGlobalSettings.ini (see here for related documentation: https://doc.castsoftware.com/display/DOC83/Appendix+-+Modifying+default+CAST+data+storage+locations)
; Set the default deploy folder location
4. Bring up each application in CMS and Verify that the Platform Settings (in Windows->settings) look good and all point to Drive D
5. In CMS, start DMT and verify if the DMT packages (upload folder) point to C Drive. If they do, then do the following (see the following for related documentation: https://doc.castsoftware.com/display/DOC83/Validate+and+Accept+the+Delivery):
- Rejected package and updated to D
- Set as 'Current Version' and updated the Deploy paths to Drive D
6. In PGAdmin: Update the 'deploypath' in the table CMS_PortF_application on the management schema
set search_path= xxx_mngt;
Update CMS_PortF_application set deploypath='D:\CAST_ANALYSIS\deploy/<application>';
7. Import Application into AIP console using the CLI below (see here for related documentation: https://doc.castsoftware.com/display/AIPCONSOLE/Import+an+Application+managed+with+CAST+Management+Studio+into+AIP+Console)
importApplication.bat -apiHost "http://<host>:<port>" -appName "<application>" -mngtSchemaName "xxx_mngt" -token "<token>"
8. In Console: make sure that all analysis units are present and all point to drive D. Make sure that all configuration files are located on drive D such as Dynamic Link filter files.
Zendesk Ticket Number