CMS Application - Delivery

This page will help you solve problems related to Delivery Tab.

This tab allows you to manage the source code deliveries (Versions) packaged either: 

• by your Delivery Managers using the CAST Delivery Manager Tool via the CAST AIC Portal
• by yourself directly from the CAST Delivery Manager Tool launched from the CAST Management Studio

Online documentation : CAST - Management Studio Help >  Infrastructure > Editors > Application Editor > Delivery tab

For more information, refer official documentation :

For 8.3 : CMS - Delivery tab

1. If you are facing issues in the delivery tab during one specific delivery action (accept delivery, reject delivery, set as current version):
   1. Identify what are the custom plugins by following the instruction of the page Delivery Manager Tool - Information - How to get the list of custom plugins
   2. For the given custom plugins, check if the associated extensions are compatible with the CAST AIP version used:
      1. Get the list of extensions installed by running the query of the page SQL Queries - Common SQL Queries - How to get the list of installed extensions
      2. For each extension, check in the release note of the technologies pages that the version of CAST AIP is correct.
2. If you are having performance issues with delivery actions (set as current version, clone, etc.), especially over time, then this may be due to the number of deliveries you have done and you should consider removing versions which you no longer need.  
1. To see your deliveries, you can go to the delivery tab in CAST Management Studio.  Here's the related documentation on this:  CMS - Delivery tab
2. To delete a version, you can see this page in the documentation:  CMS - Delete source code from a Version/Delete a Version
3. In certain environments with a large amount of concurrency and simultaneous deliveries for multiple applications sharing a single delivery folder, you may see problems accessing files such as with the following error (ParseError error with a message: Permature end of file):
   1. 
   2. To avoid these issues, you should create separate delivery folders for each application instead of sharing a common delivery folder.
4. If you are in sync with the release note, navigate in the below pages :
   
   • CMS Application - Delivery - Accept delivery
   • CMS Application - Delivery - Add version
   • CMS Application - Delivery - Duplicate version
   • CMS Application - Delivery - Manage Delivery
   • CMS Application - Delivery - Set as current version
   • CMS Application - Delivery - Warnings
5. If you do not find the information you are looking for or solution for your problem, in this page, contact CAST Technical Support with below relevant input to help CAST Support team to reproduce the issue. 

Relevant Input

1. Sherlock (CAST Support Tool (CST) - alias Sherlock) : Option Required are : Export Database (Management Database), Export logs, Export Configuration files. The Export source code option is required when an issue occurs during the set as current version with Deployment option enabled. 
2. Relevant Screenshots of the issue.