Teamsite 7.3.1 CSSDK custom log issue

Hi,

I am not able to write information in custom.log file although I've read through the IWOV suggested method. I've also read 2 threads available on devnet for the same problem but couldn't find resolution in any. Two additional points in my thread compared to earlier thread on the same topic is:
1. I am using Teamsite 7.3.1 to achieve this
2. unfortunately I do not see servletd_out.log file in TS box. So I am not even fortunate to see System.out.Println() or log.error() messages.

I have uncommented the appenders and loggers section in log4j.xml and placed it in directory "/iwhome/local/config/lib/content_center/customer_src/etc/conf/customer". I have attached my log4j.xml as txt file in the thread.

I have downloaded log4j-1.2.8.jar file containing Logger class in package org.apache.log4j and placed it in folder "/iwhome/local/config/lib/content_center/customer_src/lib"
I have created three class files and extracted them into a jar and have pleaced the jar in folder "/iwhome/local/config/lib/content_center/customer_src/lib"
Then I've executed make_toolkit.ipl, which resulted in 0 byte customer.log file creation in folder "/iwhome/local/logs/iwui"

When I execute the workflow, the functionality written in java files gets executed properly but nothing gets written in customer.log file.

This is the way I invoke logger in my java file:


package com.geam.teamsite.workflow;
import org.apache.log4j.Logger;

private static final Logger LOG = Logger.getLogger("com/geam/teamsite/workflow/CreateFileList.getName()"); 

            CSWorkarea workarea = (CSWorkarea)task.getArea();
            workarea.unlockFiles(areaRelativePaths);
            com.interwoven.cssdk.filesys.CSUpdateResult result = workarea.update(areaRelativePaths, workarea.getBranch().getStaging(), 3);
            LOG.debug("Value of result is " + result);

Please help me guys on this.
Also, Is there a CCSDK manual somewhere which I can refer to follow the IWOV principles efficiently while writing my java files.

Many Thanks,
Retesh

Find more posts tagged with

Comments

Adam Stoller

I'm not positive, but shouldn't:

private static final Logger LOG = Logger.getLogger("com/geam/teamsite/workflow/CreateFileList.getName()");

be:

private static final Logger LOG = Logger.getLogger("com.geam.teamsite.workflow.CreateFileList.getName()");

Or just create a CreateFileList object (foo) and use

foo.getName()

.

As for log files - you might check IWHOME/../ApplicationContainer/server/default/log/server.log - I believe the servletd_out.log was a tomcat thing, and now that TeamSite uses jboss you have to reference a different log file - in a different location.

As for CSSDK Manual - you have to unload the CSSDK doc jar file which will give you all the javadocs. Unfortunately (IMO) the docs are good if you know what you are already looking for, but not that great if you aren't sure and especially not that good if you're looking for examples of usage - but that seems to be somewhat the standard for javadocs, as opposed to something specifically bad about Autonomy Interwoven's javadocs.

retesh

I'm not positive, but shouldn't:
private static final Logger LOG = Logger.getLogger("com/geam/teamsite/workflow/CreateFileList.getName()"); 
be:
private static final Logger LOG = Logger.getLogger("com.geam.teamsite.workflow.CreateFileList.getName()"); 
Or just create a CreateFileList object (foo) and use
foo.getName()
.

As for log files - you might check IWHOME/../ApplicationContainer/server/default/log/server.log - I believe the servletd_out.log was a tomcat thing, and now that TeamSite uses jboss you have to reference a different log file - in a different location.

As for CSSDK Manual - you have to unload the CSSDK doc jar file which will give you all the javadocs. Unfortunately (IMO) the docs are good if you know what you are already looking for, but not that great if you aren't sure and especially not that good if you're looking for examples of usage - but that seems to be somewhat the standard for javadocs, as opposed to something specifically bad about Autonomy Interwoven's javadocs.

Hi Ghoti, Thanks for quick response Smiley Happy

but below didn't worked:


private static final Logger LOG = Logger.getLogger("com.geam.teamsite.workflow.CreateFileList.getName()");

Yes, in my server.log file I can see Sys out statements, I feel that's the way am gonna debug my code for the time being. I was earlier reffering to /logs/iwui/content_center.log file. I was able to debug my java compilation issues by viewing this log file.

I've been going thru CSSDK javadoc and struggling at the same moment as I unfortunately belong to the second league of gentleman as you described ;-) lol..

If anybody has encountered this logging issue and has resolved it by successfully generating custom.log file then pls share your success story.

Thanks,
Retesh

BIRT221 Bar Chart.png

new_report_2__cw.rptdesign

Rohan_t1

We have got this working in 7.3.1. Making things simple and getting them done first worked for us. Did you try hardcoding the value to some existing location where iwui user has permission to write?

Try following:

param name="File" value="/iwhome/abc/custom.log"/>

Also logger name="com.geam.teamsite.workflow" additivity="false" and see if it helps.

Also try

private static final Logger LOG = Logger.getLogger("com.geam.teamsite.workflow.CreateFileList.[size=2][color=#7f0055]class[/color][/size]");

Try using this LogManager as it will give you the flexibility to use logger in the classes within same package.

ClassicModelTest.rptdesign

ClassicModelTest (2).xlsx

retesh

We have got this working in 7.3.1. Making things simple and getting them done first worked for us. Did you try hardcoding the value to some existing location where iwui user has permission to write?

Try following:

param name="File" value="/iwhome/abc/custom.log"/>

Also logger name="com.geam.teamsite.workflow" additivity="false" and see if it helps.

Also try
private static final Logger LOG = Logger.getLogger("com.geam.teamsite.workflow.CreateFileList.[size=2][color=#7f0055]class[/color][/size]");

Try using this LogManager as it will give you the flexibility to use logger in the classes within same package.

Thanks Rahul.
This issue is resolved for us. The root cause of the issue was there were two jar files containing Logger class.
Actually when I didn't found lib folder in serveletd directory then I explicitly downloaded log4j-1.2.8.jar file and placed it in customer_src/lib directory. As Ghoti mentioned TS 7.3.1 uses JBoss as Application Server so OOTB installed lib file should be searched at ApplicationContainer/server/default/lib directory. When I check this path it already had log4j.jar file containing Logger.class.
Therefore, Application Server found Logger.class in multiple location which might have caused problem.
Closing this thread. Thanks Guys.