Optional Command Line Parameters – Tracing 

Use

The tracing options are designed for advanced users, to configure the tracing.

This is useful in case of problems, when the SAP Support asks for detailed tracing information.

There are two alternatives to the tracing configuration:

·        Setting the trace level with the –d option

·        Specifying a complete Properties file with tracing parameters

Procedure

-t traceConfigurationFile: A Properties file containing settings for tracing.

# logging properties of component build infrastructure

 

# formatting and logfile output is specified below

formatter[FMT]=TraceFormatter

formatter[FMT].pattern=[%s] %24d [%t] %l  %m

log[BUILD].formatter=formatter[FMT]

log[BUILD] = FileLog

 

#file name, %g is is the number in the rotating set

log[BUILD].pattern=dctoollog%g.txt

#use rotating set of 3 files

log[BUILD].cnt=3

#10 MB each

log[BUILD].limit=10000000

 

#trace levels: ALL,DEBUG,INFO,WARNING,ERROR,NONE

com.tssap.dtr.client.severity=ALL

com.sap.tc.buildplugin.severity=ALL

/ComponentBuild/Infrastructure.severity=ALL

/ComponentBuild/BuildLog.severity=ALL

/ComponentBuild/BuildTrace.severity=ALL

 

#do not modify this

com.tssap.dtr.client.logs=log[BUILD]

com.sap.tc.buildplugin.logs=log[BUILD]

/ComponentBuild/Infrastructure.logs=log[BUILD]

/ComponentBuild/BuildLog.logs=log[BUILD]

/ComponentBuild/BuildTrace.logs=log[BUILD]

 

If you specify an output file in the Properties file, the tracing information is no longer written to the standard error output, but to this file. The correct values for setting the trace level are predefined by the SAP Support. This concerns the level of detail of the tracing:

-d traceLevel. Specifies the trace level. Supported levels are:

·        ERROR – Tracing of the error messages only

·        INFO – Tracing also of the information messages

·        WARNING –Tracing also of the warnings

·        DEBUG – Tracing of the debugging data

If you specify nothing or something else, the trace level ERROR is used. This option is ignored if the option –t is used.

Example

This section specifies two scripts as examples, which use dc.bat to load (sync) a set of components from the DTR and build them. The examples are designed to illustrate how you can write your own scripts to automate the central component build.