Entering content frame

Procedure documentation Building a Component – the “build“ Command Locate the document in its SAP Library structure

Use

With this command, you trigger the build of a single development component (DC).

Prerequisites

·        The DC must be locally available, which means that it either was loaded from the DTR or exists only locally.

·        All used DCs must be available either (pre-installed) as archives or as source files. If they are available as source code, they must have been built at least once, so that the used JAR files are available.

Procedure

...

       1.      Enter the values for the parameters as described under Mandatory Options.

Mandatory Options

-c build. This option specifies the command, in this case, build.

-f configurationRootFolder: The absolute folder path, into which the development configuration was imported.

Example

For the Windows user name john and a development configuration test1, the root folder of the configuration would be:

C:\Documents and Settings\john\.dtc\test1

(provided that the storage location of the development configuration pool has not been changed).

-s compartment. The name of the SC compartment, in which the DC is located.The SC compartment is defined in the development configuration. The names are displayed in the Active DCs and Local DCs views in the Development Configurations perspective of the SAP NetWeaver Developer Studio.

When the development configuration has been generated, the name of the compartment is <software component vendor>_<software component name>.

Example

sap.com_sc1

-v vendor: The vendor of the DC, which you want to build, for example, sap.com.

-n name: The name of the DC to be loaded (synced), for example, test/dc1.

Example

For the folders and user specified above, the command would be:

dc -c build – f C:\Documents and Settings\john\.dtc\test1 –s sap.com_sc1 -v sap.com –n test/dc1

For more information on optional parameters, see Optional Command Line Parameters.

 

 

 

 

Leaving content frame