cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Logging API in XI Adapter - "ForceSingleTaceFile" option

Former Member
0 Kudos

Hello,

in our XI Adapter, I'm using the SAP Logging API as shown in the Sample Adapter. Log entries are written via class

com.sap.aii.af.service.trace.Trace

private static final com.sap.aii.af.service.trace.Trace.Trace TRACE = new com.sap.aii.af.service.trace.Trace.Trace(VERSION_ID);

I've also created a log-configuration.xml as shown in the sample.

All the trace entries are written to defaultTrace.trc, because "ForceSingleTaceFile" option is set to "YES". When I change this option to "NO" and restart the server node. I can see my own log destination in LogViewer's tree but the file is not created and the tree node is marked with a red "X".

Is there any trick to force that file's activation or something else I forgot?

Help is as always highly aprreciated and of course rewarded!

Cheers,

Matthias

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Ok, found out the reason!

The problem was the <log-controller> in log-configuration.xml wasn't defined as the package name of the logging classes

e.g.

a class

com.mycompany.xi.adapter.file.FileAdapter

only logs to a log-controller named "com.mycompany.xi.adapter.file".

Another thing:

The Sample Adapter SDA contains 2 different log-configuration.xml files. One's located in SDA\META-INF, the other is located in the RAR of the adapter. I've just kept both, but which one will be used?

Cheers,

Matthias