importconfig
Syntax |
importconfig -location|-l directoryName -configfile|-f filename [-archiveroot|-a directoryName] |
Options |
|
-location|-l directoryName |
The directory where the development configuration should be imported. If a development configuration already exists in this directory, the import fails. |
-configfile|f fileName |
The development configuration file to import. |
[-archiveroot|-a directoryName] |
The root directory of the archive pool. |
Description |
Imports a development configuration and makes it available. |
Many DC related commands work only in the context of a development configuration. Command importconfig makes a development configuration available. The required input is the target directory into which the development configuration should be imported and the development configuration file. Note that besides the XML file that contains the development configuration also, a development configuration export file can be used. Such an export file is created by the SAP NetWeaver Developer Studio. The optional parameter archiveroot is necessary if the imported development configuration refers to compartments inside the archive root. This information is stored in the configuration index file.
The configuration index file resides in the folder as the imported development configuration. In this file you see where the search for DCs is done.
Usually, the archive pool is part of the Developer Studio plug-in com.sap.tc.ap. The root directory of the archive pool is ….\com.sap.tc.ap\comp since all compartments of the archive pool are located underneath this comp folder.
importconfig -f cfg1.export -l c:\cfg1 -a nwds\eclipse\pluginsl\com.sap.tc.ap\comp
importconfig -fcfg2.export -l c:\cfg2
To check if the expected development components were found after the development configuration import, the command listavailabledcs is used.