You can import a CDT backup exported using the CDT tool to your local developer
toolkit.
Before you begin
- Before you import 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.
- Before running 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.
This option is not
enabled by default.
- 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:
cd
dtk_extracted_runtime/repository/factorysetup
find . -name "*.restart" -exec rm -rf {} \;
cd dtk_extracted_runtime/bin
bash ./loadFactoryDefaults.sh upgrade
You can import CDT only from the immediate previous version.
- Update your developer toolkit environment. For more information about updating your
developer toolkit environment, see Updating custom extensions in containerized developer toolkit environment.