CBS Logging
Usually the CBS Web UI is sufficient to check the current state of CBS. However, in some situations it is necessary to consider CBS log files. This is mainly the case when internal errors occur.
Default Logging
By default, many applications on the J2EE Engine write into the same log.
...
1. To display the log file in the Log File Viewer, start the Visual Administrator Tool.
2. Choose the node Server <node> ® Services ® LogViewer and select tab strip Runtime.
3. Navigate to Cluster ® Server <node> ® .\log.
4. Double-click on defaultTrace.trc to show the log file in the log viewer.
Usually the log file is quite large. To see only the CBS-related log entries, enter com.sap.tc.cbs in the find text field and select column and location as shown in the figure below. Choose the search button.
You can also use more specific locations like com.sap.tc.cbs.server, com.sap.tc.cbs.receiver and com.sap.tc.cbs.cbswebui to get more specific search results.
The log file mentioned above is located in the folder <drive>:\usr\sap\<SAPSID>\JC<instance number>\j2ee\ cluster\server<server number>\log.
Here <drive> denotes the drive where the J2EE Engine has been installed.
On other platforms like Unix and Linux the file path doesn’t start with a drive name.
Modifications for CBS related Logging
In the sequel information on logging settings are provided.
Usually there is no need to change the default settings. If you need to change logging settings you should contact the SAP support first. For example it is strongly recommended not to change the location of log files. Otherwise support has to invest time to find the new location.
Separate Log File for CBS
...
1. If you want to use separate log files for the CBS, start the Visual Administrator Tool.
2. Navigate to the node Server <node> ® Kernel ® LogManager.
3. In the Properties tab set the value of key SingleTraceFile_UnrestrictedLocations
a. to com.sap.tc.cbs if the value was empty before.
b. In case that the value was not empty, add com.sap.tc.cbs to the value. The locations are separated by semicolon.
4. Save the properties.
5. In order to make sure that the changes become effective, the J2EE engine has to be restarted afterwards.
Logging Settings
For the changes described below, the Visual Administrator tool is used as well.
...
1. Start the Visual Administrator Tool.
2. Navigate to the node Server <node> ® Services ® Log Configurator.
3. In the second half of the administrator tool select tab strips Runtime and Log Destination. The following entries are of interest:
a. application_sap.com/tc.CBS.Appl_readable_trc (CBS Receiver log files).
b. service_tc.CBS.Service_readable_trc (CBS Service)
c. service_tc.CBS.Service_perf_meter (CBS Service performance measurement)
d. library_tc.httpclient_readable_trc (Http client log files)
e. library_tc.httpclient_trc (Http client log files)
The entries library_tc.httpclient_readable_trc and library_tc.httpclient_trc in this list do not belong directly to CBS. Nevertheless, they may contain valuable information for problem tracking. The input field labeled Pattern contains the path of the corresponding log file.
The logging parameters like Pattern, Limit, Count, etc. are mainly of interest here.
· Limit is the maximum size of a log file (in Bytes).
· A rotating set of log files can be established by setting the value of Count higher than one. If the log file contains %g and a set of rotating is specified then %g is replaced by the log file number.
If Count is 3 and Pattern is CBSLog%g.trc the created log files will be CBSLog0.trc, CBSLog1.trc and CBSLog2.trc. In case that %g is not used, the log file number is added to the end of the specified log file.
By default a rotating set of log files is used.
Limit is set to 2000000 (approx. 2MB) and Count to 10. This means, if the first log file is full, the second log file will be created up to the 10th log file. If the 10th log file is full then the first log file will be overwritten, then the second log file and so on.
File Path Starts With a Dot
If the file path starts with a dot then the root directory is the J2EE root path. Usually the J2EE root path (on Windows platforms) is:
<drive>:\usr\sap\<SAPSID>\JC<instance number>\j2ee\cluster\server<server number>\
Underneath the root path the subdirectories log\applications\sap.com\tc.cbs.receiver and log\applications\sap.com\tc.cbs.cbswebui and log\services\tc.CBS.Service and log\libraries\tc.HttpClient contain the corresponding log files.
File Path Starts With a Slash or Backslash
If the path start with a slash “/” or backslash “\” then the file path is located directly under the drive where the J2EE engine is installed (at least on Windows platforms). An absolute path can be specified as well for log files.
Adapt Other CBS Related Logging Settings
...
1. To adapt other CBS related logging settings, select tab strip Runtime and tab strip Categories.
2. In the displayed tree go to ROOT CATEGORY ® Applications ® tc ® CBS ® Service.
3. Underneath this level, select the node labeled Admin to adapt logging settings.
For example you can add / remove destinations and set severity (default warning).
The severity has an impact on how much information is written to the log destination. In case of severity Error, only error messages are written. If severity Debug is chosen then in addition to error messages also debug messages are written. In the last case the number of messages can be quite high. The amount of CBS logging data that is written has an impact on CBS performance.
To set severity to Info or Debug is only recommended in case of problem tracking.
If you have separate log files for CBS, you can analyze them via log viewer as described above.