You can use the Design Code Utility to transfer source code from one Commerce Cloud instance to another. This can be useful for promoting source code from a test environment to production.
To use the transfer feature, you must execute a grab from the source instance, for example:
dcu --grab --clean --node http://sourceInstance--userusername--passwordpwd
After the grab is finished, you transfer the files to the destination instance, using a command similar to the following:
dcu --transferAllpath--node http://destinationInstance--userusername--passwordpwd
Design Code Utility takes a “best effort” approach to transferring content between instances. In general, it matches by name so that if, for example, a widget instance on the destination instance has the same name as a widget instance on the source instance, they are assumed to be the same. The matching rules for each entity type are described in the table below.
Type | Matching rules |
|---|---|
Global elements | Matches on the |
Application-level JavaScript modules | Matches on the JavaScript file name. If the file name does not exist, it is created on the destination instance. |
Text snippets | Matches on locale. |
Stacks | Matches on the stack instance’s display name. If the stack instance does not exist, a warning is issued. |
Themes | Matches on the theme name. If a matching theme does not exist, one is created on the target instance, using the same name and source code. |
Widgets | Widgets are matched on version number and display name. If the widget does not exist, a warning is issued. Widget instances are matched on display name. If a matching widget instance does not exist, a new widget instance is created on the target instance using the same display name and source code. |
Elements | Widget elements are matched on version number, display name and |
