Skip to end of metadata
Go to start of metadata

Log and Trace files of the Deploy Controller:


This is the Deploy Controller log file. No other component writes messages in it. By default its severity level is "INFO" and it describes all the relevant steps of the deployment flow. The file does not contain stack traces however, so if there is an error in it you should have a look at the deployment trace for the details. The information included here is for both the online and the offline phase of the deployment process.


This file is much like the log file with the difference that the severity level here is "WARN" and the stack traces are also included. The file can be helpful for the discovery of the root cause of an error message that you saw in the deployment log file. The information included here is for both the online and the offline phase of the deployment process.


This file contains some more specific offline deployment information about uploading, validation and delivery of offline deployment items.

The server log:

/usr/sap/<SID>/<IN>/j2ee/cluster/server*/log/server_xx.x.log -

This is the AS Java log file. Each node has a separate log file where it logs messages.
The category that Deploy Controller uses is /System/Server/Deployment

The Default Trace of the server:

/usr/sap/<SID>/<IN>/j2ee/cluster/server*/log/defaultTrace.*.trc -

The default trace of AS Java is always a good place to have a look at when you have problems. Some of the errors that we get in the deployment process could be related to some DB or security issues. If it is not clear what was the exact reason for the failed deployment it might be worth looking at the default trace and examining the messages that were written around the time the deployment failed. One problem with the default trace is that it is not written in a human readable format and has to be converted. The loggging location used by Deploy Controller is

These are some logs written by the startup framework and related to the Offline deployment only:


The information in this file can be used to confirm that the offline phase deployer has been executed upon system startup.


The log files are related to the JVM execution of the Offline deployment process


This log file shows what was the offline deployment main class and from which JAR files the classes needed for the offline deployment were loaded.

Deploy Controller client logs:

The location of the Deploy Client logs depends on the application that is client of the Deploy Controller.

  • If the application does not provide its own logger, the logs are stored in the default location: ${work.dir}/log/dc_log

where the "." presents the directory where the Deploy Controller client has been started.

  • It is possible that the application, using the Deploy Controller, provides its own logger implementation but does not generate the dc_log folder. So, if you cannot find the dc_log folder somewhere in the working directory of the application contact the people, responsible for the application and ask them to show you where the logs are.

The Deploy Controller service is logging its information into log files where many other components are logging their data.

Log Viewer Tool
In order to easily monitor what is happening on AS Java you need to use the log viewer tool. A detailed guide of its usage and features can be found here. The log viewer is integrated within the SAP NetWeaver Administrator (NWA) which is accessible through a web browser. You are given the options how to search and configure the logs and traces mentioned above.

Alternatively, you can use the command-line version of the log viewer in order to filter only the Deploy Controller related information from a specific log file with the following command:

  • No labels