nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I log TBO DFLogger messages to the content server?

jklawrence

I have a TBO installed that appears to work fine when it is called from Webtop. I have logging set up and can see log statements on the application server.

However, I have a Java program that runs and updates some content. Something is going on with the TBO that I can't see, and I would like to be able to log the TBO steps to the content server. I've tried modifying the log4j files in the serverapps.ear directory but that hasn't helped. Is there a way to see what's going on?

- Jane

Find more posts tagged with

Comments

DCTM_Guru

TBO is executed at client (app server) level, since it intercepts the calls before calling the server. AFAIK, you can only log to app server and log4j.properties is appropriate place for your config changes. If you post your log4j, we can try to verify that the syntax is correct.

jklawrence

Thanks, Johnny. I have log4j.properties set up in the Webtop app, and I am getting logging when I do a checkout/checkin through Webtop. However, when I run my Java code, which also does a checkout/checkin, no logging is being written.

## Custom logging for Legacy Object Model TIC doc TBO

log4j.logger.TicDocTBO=DEBUG,TicDocTBO log4j.appender.TicDocTBO=org.apache.log4j.RollingFileAppender

log4j.appender.TicDocTBO.File=c\:/Documentum/logs/TicDocTBO.log

log4j.appender.TicDocTBO.MaxFileSize=100MB

log4j.appender.TicDocTBO.layout=org.apache.log4j.PatternLayout

log4j.appender.TicDocTBO.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss,SSS} %p %c %m %n

DCTM_Guru

Where are you running the java code? If you are running java code your local computer, then log4j.properties has to be on the local computer.

jklawrence

That makes perfect sense. However, when I added the above code to my local log4j.properties file I'm getting an error that my code cannot instantiate the appender. I did add the apache log4j.jar file to my Composer project library. I've looked around for some documentation or a tutorial on how to set this up and haven't found anything. Are you aware of any documentation on setting this up locally?

Thanks.

DCTM_Guru

Try this link:

http://developer.emc.com/developer/Component_Exchange/downloads/DfLogger-Enable_Console_Logging.pdf

jklawrence

Thanks, that was a big help.

I have the logger set up in my local log4j.properties file, and the file is being created, but no messages are being logged from my java program.

My log4j.properties file includes:

## Custom logging for Import For OCR stand-alone java program log4j.logger.gov.nps.documentum.ImportForOCR=DEBUG,ImportForOCRLogger log4j.appender.ImportForOCRLogger=org.apache.log4j.RollingFileAppender log4j.appender.ImportForOCRLogger.File=c\:/Documentum/logs/ImportForOCRLogger.log log4j.appender.ImportForOCRLogger.MaxFileSize=100MB log4j.appender.ImportForOCRLogger.layout=org.apache.log4j.PatternLayout log4j.appender.ImportForOCRLogger.layout.ConversionPattern=%d{dd MMM yyyy HH:mm:ss,SSS} %p %c %m %n

Then I have statements in the code like:

DfLogger.debug("ImportForOCRLogger","FetchFilesForProcessing.getFiles test message",null,null);

Nothing is being logged. If I change the class to com.documentum.fc I get a lot of logging.

Can you tell me what I'm missing?

- Jane

After I posted this, I found this link:

https://community.emc.com/thread/70839

I, too, am able to write using trace but not debug

With trace, I'm seeing messages, but it still isn't helping me with the TBO debugging. Here's the problem:

14:03:12,658 [main] FetchFilesForProcessing.importFiles, object name is LAME_602_C46 417438

14:03:13,088 [main] FetchFilesForProcessing.importFiles, changed doc object name is LAME_602_C46

14:03:13,138 [main] FetchFilesForProcessing.importFiles, changed doc object name before save is LAME_602_C46 417438

14:03:13,188 [main] FetchFilesForProcessing.importFiles, changed doc object name after save is LAME_602_C46

The object name is being modified by the save. I have found that if I do a checkout and chekin with a different version, the name is fine, but if I do a checkout and checkin SAME_VERSION, the name is modified. If I do the same process through webtop (checkout, checkin same version), everything is fine. I'm trying to figure out what's happening behind the scenes.

Message was edited by: jklawrence

aflowers001

You probably need to change the debug setting in your local dfc.properties file. Take a look at dfcfull.properties (if memory serves) for the debug setting in there. these allow you to tuen on dfc level diagnostics to see the flow of what is around the TBO and what the calls within the TBO are actually doing.

jklawrence

Thanks for the suggestion. I added

dfc.logging.level_to_force_stack=ALL

and

dfc.tracing.log.level=ALL

but I'm still not getting anything at all from the TBO, just the entry point for my java program.