Page tree

Versions Compared


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


The following image shows the structure of the existing and AIP Console Delivery folder formats. In essence, the new format allows each Application to have a specific "plugins" folder, which in turn allows more flexibility with regard to the extensions that can be used with an Application:

Usage instructions

Instructions for using the tool are provided in Import an Application managed with CAST Management Studio into AIP Console.

Technical information

Applications skipped in migration

The following Applications will be skipped during the migration process

  • Any Applications that have no delivered source code
  • Applications that have a duplicate management ID in index.xml (this file is located in the existing Delivery folder)
  • Applications whose management ID is not present in the Management schema
  • Applications with duplicate management IDs at schema level (same management ID present in different schema or across server)
  • Applications present in the Management schema whose schema name is not in align with site_name in the sys_site table

Errors / warnings

Error / warnings

ERROR --- old delivery folder does not exist - C:\OldLocationEnter valid and existing old delivery folder location.Input Validation Error
ERROR --- new delivery folder does not exist - C:\NewLocationEnter valid and existing new delivery folder location.Input Validation Error
ERROR --- Config file should be a valid json file.Config file provided should be json format (.json).Input Validation Error
ERROR --- Old Delivery Folder should have index fileOld delivery folder should have index file.Input Validation Error

ERROR --- size of new directory is less than that of old directory

There is not enough space in new delivery folder. Check the size.Input Validation Error

WARN --- Schema Doesn't have CMS_PREF_SOURCES relation

This occurs when schema do not have table 'cms_pref_location'CastMSDatabaseConnection
WARN --- Schema Name is not matching with Site_Name from Sys_site table hence excluded from migrationDifference in schema name fetched from database provided in config file and site_name in sys_site table. Applications with this issue will not be migrated. CastMSDatabaseConnection
WARN --- Please remove one MNGT schema for the MNGT id to proceed furtherThis occurs when same management id is present in more than one management schema.CastMSDatabaseConnection

Info provided to user

In addition to splitted application folders, the tool generates the below files at new delivery folder location after run is completed This file contains summary of the run with below attributes :

ProcessCompletedThe value is true if the process is completed successfulyy else false
Skipped.Applications.DuplicateMngtID.NameSkipped Application Info that have duplicate management id
LatestMigratedApplicationIDlatest id of application which is migrated.
Size.oldDeliveryFolderrepresents size of old delivery folder
Skipped.Applications.Undelivered.NameSkipped Application Info that are undelivered
Count.Applications.toBeMigratedcount of eligible application that is to be migrated
Size.newDeliveryFolderrepresents size of new delivery folder
Count.Applications.skippedcount of skipped application that are not migrated
Count.Applications.overallcount of overall application present in index.xml file
Count.Applications.migratedcount of application that are migrated after the process is completed.
Skipped.Applications.MissingMngtID.NameSkipped Application Info whose management ID is not present in database across schema/server

ApplicationInfo : This text file contains the detailed info of Application that are skipped in migration process.

delivery-folder-migration-tool-logs : This file contains complete log.

index.xml This is created directly under new delivery folder location that contains mapping of uuid and app name for all the migrated application. Sample as below : 

Image Added

When user rerun the migration.bat file these migrated apps are read from this index.xml file and skipped in next run.

This prevents the repopulation of new delivery folder with existing applications in each run.

Key Points : 

In case of abrupt failure at any application while migration, the application mapping will not be populated in newDeliveryFolder location index.xml file.