Importing configurations by using Configuration Deployment Tool (CDT)

You can import a CDT backup that you downloaded from the Sterling™ Order Management System environment to your local developer toolkit.

Before you begin

Before you import the configurations from a CDT backup directory, ensure that the version of your CDT backup is compliant with the version of your developer toolkit environment. Otherwise, the CDT import task can render your environment unusable.
Warning: Importing CDT data is allowed only from one version older than the current version as an exception. However, any CDT import from a different version has risks associated to it.
Before running the CDT import, it is recommended that you bring down all your application and agent servers. You can bring up the servers after the CDT import is done.

Procedure

Ensure that you have a copy of the extracted runtime. For information about extracting the runtime from your Docker container to your host machine, see Update custom extensions in containerized developer toolkit environment.
To import configurations from a CDT backup to your developer toolkit environment, run the following CDT command from your <extracted_runtime>/bin directory:
bash ./cdtshell.sh -Source DEFAULTXMLDB -Target SYSTEMDB -DefaultXMLDir <Full path to CDT backup directory>
As part of your CDT deployment, if you have abandoned records and want to clean them up, pass the -ShowAbandoned Y option when running the cdtshell.sh command.
By default, this option is not enabled.
If CDT is imported from a lower version, you must reload the factory data of the current version again in upgrade mode, by running the following commands from the devtoolkit_docker/runtime directory.
1. cd dtk_extracted_runtime/repository/factorysetup
2. find . -name "*.restart" -exec rm -rf {} \;
3. cd dtk_extracted_runtime/bin
4. bash ./loadFactoryDefaults.sh upgrade
You can import CDT only from the immediate previous version.
If developer toolkit is integrated with Sterling Intelligent Promising Inventory Visibility, the Sterling Intelligent Promising Inventory Visibility adapter phase must be updated correctly in the developer toolkit after importing configurations from a CDT backup. This is required if the phase of your CDT source is different or if you have run the steps listed in step 3.
- If developer toolkit is integrated with Sterling Intelligent Promising Inventory Visibility adapter phase 2 (default), run the following command from runtime/bin:
```
bash ./sci_ant.sh -f configureIVIntegration.xml -DNewCustomerImplementation=true
```
- If developer toolkit is integrated with Sterling Intelligent Promising Inventory Visibility adapter phase 1, run the following command from runtime/bin:
```
rm -rf ../repository/factorysetup/iv_integration/install/*.xml.restart && 
bash ./loadDefaults.sh ../repository/factorysetup/iv_integration/install/iv_baserules_installer.xml 
../repository/factorysetup/iv_integration/XMLS/
```
Update your developer toolkit environment. For more information about updating your developer toolkit environment, see Update custom extensions in containerized developer toolkit environment.