CBS Service Properties

Use

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.
ENVIRONMENT_VARIABLES		There are three ways to specify how CBS passes environment variables to the DC build process: ( Default ) Leave this CBS service property empty. In this case CBS does not pass environment variables to the DC build process. This default equates to the CBS behavior before CBS service property ENVIRONMENT_VARIABLES was introduced. As long as you do not face DC build issues linked to missing environment variables you can leave this service property empty. Enter the string null : the CBS passes the environment variables of its process to the DC build process. Enter a comma (,) separated list of environment variables. If only an environment variable name is specified its value is read from the system by CBS (see Example 2). In case the specified environment variable is not defined in the system environment, it is skipped. If you want to use the separator characters equal (=) and semi-column (,) as value, they need to be escaped using backslash (\). The examples below refer to Microsoft Windows as operating system (OS). The environment variables you defined are OS dependent. Example 1: TEMP=C:\Temp,SystemRoot=C:\WINDOWS Example 2: TEMP=C:\Temp,SystemRoot,PATH
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. Note Use node id as suffix to root folder to have a unique name because there is no locking in CBS cache. This may lead to inconsistencies especially in cases in which a root folder is shared between nodes. Rename .CACHE folder to .C (similar to .B which stands for build ) to shorten the paths. This is important for Windows OS, because of the 250 chars restriction. Allow multiple paths in rootFolder configuration so that every server node picks one. For example, c:\root; D\root;
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. Caution In old SAP NetWeaver versions, you could set this property per instance node. For example, if you have 4 CPUs and 2 server nodes you configure server0 to 2 and server1 to 1 worker thread (rule of thumb is worker_threads=max_cpus -1). However, in this SAP NetWeaver version this can be set on instance level only . You set the thread pool size for a single instance, but this affects each and every server node process. For example, if you have 4 CPUs and take 3 you expect that the threads are automatically distributed among the 2 server node processes. In fact each server node will get 3 worker threads which resulted in a maximum of 6.
useClassicSync		Specifies whether to use normal sync (true) or Virtual File System sync (false value).