Loggin and tracing APIs - runtime dependency

[former_member190457]

Hi developers,

I would like to use Tracing and Logging APIs in my EJBs.

EJB DCs should depend on tc/bl/logging/api for build time api access

What are the ear runtime dependencies required for logging library usage?

Thanks, regards

Vincenzo

[rolf_paulsen · Accepted solution]

Hi Vincenzo,

there is no need for a runtime-dependency. This stuff must be in the system-Classloader of the Appserver. (7.20 SP3)

If you want to use it in standalone clients, see sap.com_tclogging_javaimpl.jar in j2eeclient-dir on Appserver.

Regards

Rolf

[former_member190457 · Accepted solution]

Hi Rolf

I'm on CE 711 SP5, is that true also for this release?

Thanks, regards

Vincenzo

[rolf_paulsen · Accepted solution]

Hi Vincenzo,

I am 99,99% sure, but cannot check it. Why should they have changed this?

Regards

Rolf

[former_member190457 · Accepted solution]

Thanks, Rolf.

One more question: I have added a static variable of class Location to my EJB like

private static final com.sap.tc.logging.Location logger = 
com.sap.tc.logging.Location.getLocation(myClass.class);

Now I can't find this location in NWA -> log configuration -> tracing locations.

On the other hand, in that view I can see all the web dynpro Tracing locations.

What am I missing?

Thanks, regards

Vincenzo

[rolf_paulsen · Accepted solution]

Hi Vincenzo,

the Location defined by com.sap.tc.logging.Location.getLocation in your code is shown in the Location columnt in Log Viewer, e.g. Default Trace (Java).

The Trace location in the log configuration has nothing to do with this Location - it is the file location of the file that you will not want to define per class. (Which strategy and granularity SAP uses for WD and how to find the correct file location in the Trace location - sorry, no idea.)

Regards

Rolf

[former_member190457 · Accepted solution]

thanks again Rolf.