Name

Proposed Value

Description

AdminTaskDelay

5000

Specifies the time interval (in milliseconds), after which to check for new build requests.

BUILD_TOOL_JDK_HOME

Highest required JDK version. For example, if you need to build on the same CBS using JDK 1.4 and JDK 1.5, this should point to the JDK 1.5 installation.

The path to the JDK installation directory of the JDK that will be used by the build plug-in to perform the actual build.

BUILD_TOOL_VM_ARGS

-Xmx1000M

Virtual machine arguments for build tool process.

cleanUpRequestFolders

Specifies whether to remove the content of the folder after the build. As a rule of thumb, each build request consumes approximately 15 MB disk space.

idleStart

true

When set to true the Component Build Service (CBS) does not process any requests.

JDK_HOME_PATHS

Check 1.5 JDK installation.

JDK installation directory to use for the build.

A semicolon-separated list of JDK home installation directories. A default JDK can be specified by using the key word default.

See also the build-option com.sap.jdk.home_path_key under Build Options.

JDK1.5.0_HOME=C:\jdk1.5.0

In case more than one JDKs need to be supported:;
JDK1.4.2_HOME=C:\jdk1.4.2;
JDK1.5.0_HOME=C:\jdk1.5.0;
default=C:\jdk1.5.0

notifyTCS

true

Specifies if there will be notification of the new build results.

On the backend, the Change Management Service (CMS) of the NWDI runs on an AS Java. Technically, it is split into a Propagation Control Service (PCS) and a Transport Control Service (TCS). The TCS controls the automatic build process in the CBS and deployments in the runtime systems. The Software Deployment Manager (SDM) is responsible for the actual deployment of your software. The notification of the Transport Control Service (TCS) is required for the automatic deployment.

rootFolder

The folder in which to execute the build requests, for example, the directory where files will be stored to perform a build.

We recommend that you use a location with a short path on a dedicated, fast hard drive for optimal performance.

tcsQueueCheckDelay

The period in milliseconds, after which to check if there are build requests for which that has not been sent notification.

threadPoolSize

Up to number of CPUs -1.

Number of requests that can be processed in parallel from the build. This also means the number of BUILD_TOOL_JDK_HOME VMs that may be started on the AS Java host.

useClassicSync

Specifies whether to use normal sync (true) or Virtual File System sync (false value).