CMS Application - Delivery - Set as current version - Deploy source code - Performance issue

Mon, 01 Jan 0001 00:00:00 +0000

*Purpose

This page will help you to troubleshoot performance issues you can face during the Set as current version.

*Observed in CAST AIP

Release	Yes/No
8.3.x	✅

*Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Action Plan

Check if there is performance issue on the machine where you set as current version by using the Task manager tool, in the Performance tab. If yes, check what the process that are consuming too much ressources and kill them.
If the deploy folder is on the local machine :
1. Check if the the files to be deployed are not in only one folder.
2. If yes, and if the technology does not constraint to get all the file in only one folder, the source code must be splitted in multiple folders.
3. Then package the source again and set as current version again.
If the deploy folder is on server machine :
1. Make sure that the files transfer between your machine and the server is quick enough.
2. If it is not quick, it is expected to get performance issue.
3. If it is quick, check if the the files to be deployed are not in only one folder.
4. If yes, and if the technology does not constraint to get all the file in only one folder, the source code must be splitted in multiple folders.
5. Then package the source again and set as current version again.
Navigate to the below pages :
If you do not find the information you are looking for or solution for your problem, in this page, contact CAST Technical Support with Delivery Manager Tool - Relevant Input for Support to reproduce.

Notes/comments

CMS Application - Delivery - Set as current version - Deploy source code on Documentation - V2