Logging Format like in default trace

Hi all,
When using log-viewer service in visual admin I want my logs to be formatted as it is in default trace (defaultTrace.trc)
The message is separately displayed in its own column whereas location/severity/date etc. is shown in its own column, but not contained in the message itself.
When I use my own location, destination(file) and formatter(trace) I cannot achieve the same. I get date and time in the right columns, but in the message column I get all the stuff that is in the file: date, severity, location. Let's say its not getting filtered.
Any idea what's so special about default trace?
regards
stefan
Edited by: Stefan Bungert on Apr 21, 2008 4:16 PM

Hi,
I think you change the format as you using TraceFormatter class.
According to the pattern you give in the constructor your format will change.
It is that pattern that determines.
Regards,
Srinivasan Subbiah

Similar Messages

Data log format like JDK logging

Hello:
I'm working with SUNONE AS
Source classes belong my application use Java logging ( JDK 1.4.2 ) , but logs ( in instance's server.log ) don't be written in Java logging format, i.e, class name & method name where log method ( by example, info() ) call is invokated
How can I do for logging calls into my code to write in Java logging format ? How I can to configure my SUNONE AS ? Must I change logging properties file in jre/lib ?
Thanks in advance
Best regards

Hi,
I think you change the format as you using TraceFormatter class.
According to the pattern you give in the constructor your format will change.
It is that pattern that determines.
Regards,
Srinivasan Subbiah

Our Portal development system is logging huge default trace

Hi all,
We are experiencing huge logging on our Portal server. This is a NetWeaver 7.0 SP15 Java only system. The default trace is filled with this notification and it logs about 10MB every few minutes.
#1.#005056A13EB0002700124860000027D90004617318B4F29F#1233046870487#com.sap.engine.services.connector.resource.impl.MCEventHandler##com.sap.engine.services.connector.resource.impl.MCEventHandler####n/a##f3ffb870e86b11dd9c7b005056a13eb0#SAPEngine_System_Thread[impl:5]_71##0#0#Debug##Java###>>> [email protected]f975f9 --> 57(locTrSupp:false).cleanup({0}), shared: {1}, destroyed {2}, invoked from: {3}#4#true#false#false#java.lang.Exception
        at java.lang.Throwable.<init>(Throwable.java:58)
        at com.sap.engine.services.connector.Log.getStackTrace(Log.java:61)
        at com.sap.engine.services.connector.resource.impl.MCEventHandler.cleanup(MCEventHandler.java:358)
        at com.sap.engine.services.connector.resource.impl.MCEventHandler.dissociateAfterLocalTransaction(MCEventHandler.java:815)
        at com.sap.engine.services.connector.resource.impl.MCEventHandler.localTransactionCommitted(MCEventHandler.java:508)
        at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.clientCommit(LocalTXManagedConnectionImpl.java:585)
        at com.sap.engine.services.dbpool.cci.ConnectionHandle.commit(ConnectionHandle.java:206)
        at com.sap.caf.eu.gp.base.db.TransactionController.updateTransaction(TransactionController.java:215)
        at com.sap.caf.eu.gp.base.db.TransactionController.closeTransaction(TransactionController.java:147)
        at com.sap.caf.eu.gp.base.db.TransactionController.closeTransaction(TransactionController.java:133)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorPersistenceImpl.closeTransaction(CallableObjectExecutorPersistenceImpl.java:139)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorPersistenceImpl.readOverdueTasks(CallableObjectExecutorPersistenceImpl.java:621)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorTimeoutProcessor.process(CallableObjectExecutorTimeoutProcessor.java:158)
        at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorTimeoutProcessor.run(CallableObjectExecutorTimeoutProcessor.java:205)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
How can we solve this?
Best regards,
Jan

Hi,
maybe you didn't explicitly installed Guided Procedures (GP), but the Java error is from GP. The Java classes:
- com.sap.caf.eu.gp.base.db
- com.sap.caf.eu.gp.model.co.execute
are Guided Procedures (caf.eu.gp). In NetWeaver 7.0 - I believe - the Guided Procedures are installed more or less by default.
Check if you have the following folder in your PCD:
- pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp
and check if you have applications (Java AS) installed like:
- sap.com/cafeugpuiadmin
- sap.com/cafeugpuirtwc
- sap.com/cafeugp~*
If so, the GP are installed. If you can't deinstall them via NWA try to configure them correctly:
http://help.sap.com/saphelp_nw70/helpdata/EN/89/d084428254b767e10000000a155106/content.htm
br,
Tobias

Error Logs in the Default Trace

Hi All,
Iam getting following eror for every second in the Default Trace log but no users are effected with this log. Can anybody tell me what this error is about .
Date : 12/20/2006
Time : 11:18:43:702
Message : Exception in method: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
[EXCEPTION]
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
     at java.lang.Thread.run(Thread.java:534)
Severity : Error
Category :
Location : com.sap.ip.collaboration.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()
Application : sap.com/irj
Thread : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
Datasource : 34368150:/usr/sap/PP1/JC03/j2ee/cluster/server0/log/defaultTrace.trc
Message ID : 0003BA4DBF04001100003473000012530004250B918DE14E
Source Name : com.sap.ip.collaboration.rtc
Argument Objs : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
     at java.lang.Thread.run(Thread.java:534)
Arguments : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
     at java.lang.Thread.run(Thread.java:534)
Dsr Component :
Dsr Transaction :
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.ip.collaboration.rtc
ThreadObject : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
Transaction :
User : j2ee_guest
Thanks,
Master

I am having this same issue as well. I upgraded our BI and BI Portal to SP12. Everything worked fine. Then I started the BI integration as outlined in OSS note 917950 -> Setting up BEx Web - Problem analysis.doc and restarted the J2EE engine and now I have this same error in the default trace and I can't log into the visual admin as the j2ee_admin user. I get "error while connecting".   But I can connect to the visual admin as myself. If I login to the BI portal as my self and click on user administration I get this error "A required service for the identity management user interface is not available. Contact your system administrator"
Here's the error as seen in the default trace file that keeps repeating.
#1.#0003BA21A6F5005C000000590000595B000439DE957600B4#1189528059902#com.sap.ip.collaboration.rtc#sap.com/irj#com.sap.ip.collaboration
.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()#J2EE_GUEST#0####d71a1250608111dcbcf70
003ba21a6f5#Thread[Thread-57,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Java###Exception in method: com.sap.engine.se
rvices.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfa
ctory/default/QueueConnectionFactory.
[EXCEPTION]
#1#com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the wh
ole lookup name is jmsfactory/default/QueueConnectionFactory.
        at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
        at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
        at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
        at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
        at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
        at javax.naming.InitialContext.lookup(InitialContext.java:347)
        at javax.naming.InitialContext.lookup(InitialContext.java:347)
        at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1238)
        at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1182)
        at java.lang.Thread.run(Thread.java:534)
Also, at the very beginning of the default trace file I see this error:
##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
[EXCEPTION]
#1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null
##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
[EXCEPTION]
#1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null

Write logs in different location instead of default trace

I need to write a logs in different location other than default trace. I don't want to write logs in default trace. what setting i need to do in portal so that i can able to write at other location instead of default trace.

Hi,
Check this thread.
Log for J2EE Web Services?
Regards,
Harini S

Unable to view latest default trace in log viewer

Hello all,
We have NW 7.0 J2EE production server. We have a CI and two application servers.
Our SP level is SP18.
The DB is oracle and the operating system in RHEL 4.
I have a problem in viewing the default trace files in log viewer using the visual administrator.
I am able to view the old default trace but unable to view the latest trace data generated.
I am facing this problem when i try to view the logs of a particular application server.
Able to view the latest default trace properly for CI and the other application server. Problem lies only with a single application server.
I have also check the permissions in OS level for the trace files. Everything looks fine.
Could some one give me a clue on how to solve this issue.
Regards,
Chandru

Hello Joey,
The trace file isnt too big....
We have set the file size as 10 MB.
We have some 15 to 16 default trace files for each of the server process and we have 3 server process in that application server.
The ForceSingleTraceFile parameter is set as YES in visual admin.
So the logs will be displayed in visual admin as a single default trace file.
Hope I had provided the inputs you have asked...
Regards,
Chandru

NWA logs and trace does not show the content of Default trace

Hi All,
The content which i see in /usr/sap/SID/DV*/j2ee/cluster/server0/log/default trace
i am unable to see the same in default trace in NWA logs and traces,
It is a 7.0 system..
Coudl you please suggest.
Rgds
S

Hello,
Is it newly built system? Please compare log and trace levels with other java systems in your landscape.
You can give a try as following..
       1.      Goto NWA and click on Log Configurator service.
       2.      Switch to advanced mode.
       3.      Select the Location tab page.
       4.      Choose the location of default.trc file.
       5.      Save the configuration
       6.      Restart JAVA and see.
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Jan 12, 2012 3:36 PM

Default Trace and system Log

Hi all,
I have got default trace and system log folders
Default trace - \usr\sap\J2E\JC00\j2ee\cluster\server0\log\.
Security log - \usr\sap\J2E\JC00\j2ee\cluster\server0\log\system
I need to know are these folders specific to setup package created . I mean can i get these folders for one i created on specified date.
Answers would be rewarded
Thanks and Regards
Neha Kapoor

The problem is solved

Workflow Daemon is stuck in E sourcing CLM and documents are not flowing to approvers.which place should i check for this issue related information i have already checked default traces and Logs

Hi Guys,
We have a situation in our landscape where workflow daemon service is stuck and we have to restart the Esourcing system.
Could you please help here where should i check the cause of the issue.
i have already checked the Default traces and Esourcing traces.
Could you help in identifying the cause.
Regards
Tarun

Hi Tarun,
Open the Document for e.g. Contract Document, on the Document Tab there is an option for Phase Information open that page this will give you all the information related to the phase and where it is stuck, with which user it is pending etc.
Now since the workflow is stuck, either you can restart the Demon Registration via background Task Status. or else Cancel the Workflow so it can be restarted. by doing the below steps.
1) goto Setup
2) open Workflow Definition Under Workflow.
3) now choose the phase at which your Workflow is stuck.
4) open that phase.
5) under Reports Tab there is option for " Current Workflow Processes"
6) open the Current Workflow Processes
7) search the document which is stuck
8) click on the "X" mark = Cancel the workflow process option
9) it will take you to the workflow cancel wizard screen. give the comment why you need to cancel this and click on Finish
10 ) once the Workflow is canceled the phase will go to the Requester review phase and form here you will have to manully move to the next phase. so the workflow can be restarted. once done refresh it.
11) before doing this take Approval from the customer.
If the above does not work and still there is an issue then please check the Pre- Phase script.
Let me know if this works.
Thanks
kanchan

Time stamp information in default trace file

How to check the time stamp in defaulttrace.trc or application.trc files for logs in XI server.
I have seen following timestamp in above mentioned trace files. But seem to me, during the shutdown time of server, system put the timestamp in trace file.
ERROR       gateway shutdown
TIME        Fri Jun 20 11:01:08 2008
Except for shutdown time, how the system put the timestamp for other activity of system in the default trace and application trace file??
Sometime, i need to check the timestamp to get some specific information in default trace file for some system activities.
is timestamp mentioned in coded form as per following log:
#1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS                          #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
lain###java.lang.reflect.InvocationTargetException#
#1.#36CC34C00F02009B000001B500001FF40004510B33EAB76C#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS                          #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
lain###java.lang.reflect.InvocationTargetException
Thanks
Amar

Hi Amarjit
The timestamp is noted in unix epoch time (java does use this as well). It is this field:
#1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3# 1215008464352 #com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS
The first 10 digits are seconds since epoch. The last 3 digits are milisecondes. Converted in human readable format: 07/02/2008 16:21:04.352
[Unix Time|http://en.wikipedia.org/wiki/Unix_time]
Damn, i remeber having answered this already here in the forums, but i cannot find the thread anymore myself :-(((
Best regards
Michael

Default trace?

Hi Friends,
usr/sap/<sid>/DVEBMGS<nn>/j2ee/cluster/server0/log/archive
In the above folder the default trace files of XI are getting archived, which is zip format and in hidden mode.These files have occupied huge amount of space.
What is the importance of these files?
Are these files necessary?
Will it cause any problem if we delete these file?
Pls help !!
Regards,
Bharath.

Hai,
Check the below link.....
http://help.sap.com/saphelp_nwce10/helpdata/en/ac/e9d8a51c732e42bd0e7de54b9ff4e2/frameset.htm
You can delete the old archives if you really dont see any issue.
Regards,
Yoganand.V

Is this logging code faster than using a standard logging API like log4J

is this logging code faster than using a standard logging API like log4J or the logging API in java 1.4
As you can see my needs are extremely simple. write some stuff to text file and write some stuff to dos window.
I am thinking about using this with a multi threaded app. So all the threads ~ 200 will be using this simultaneously.
* Tracer.class logs items according to the following criteria:
* 2 = goes to text file Crawler_log.txt
* 1 = goes to console window because it is higher priority.
* @author Stephen
* @version 1.0
* @since June 2002
import java.io.*;
import java.net.*;
import java.util.*;
import java.text.*;
class Tracer{
public static void log(int traceLevel, String message, Object value)
if(traceLevel == 1){
System.out.println(getLogFileDate(new Date()) +" >" + message+ " value = " + value.toString()););
}else{
pout.write(getLogFileDate(new Date()) +" >" + message + " value = " + value.toString());
pout.flush();
public static void log(int traceLevel, String message )
if(traceLevel == 1){System.out.println(message);
}else{
pout.write(message ) ;
pout.flush();
//public static accessor method
public static Tracer getTracerInstance()
return tracerInstance;
private static String getLogFileDate(Date d )
String s = df.format(d);
String s1= s.replace(',','-');
String s2= s1.replace(' ','-');
String s3= s2.replace(':','.');
System.out.println("getLogFileDate() = " + s3 ) ;
return s3;
//private instance
private Tracer(){
System.out.println("Tracer constructor works");
df = DateFormat.getDateTimeInstance(DateFormat.MEDIUM, DateFormat.MEDIUM);
date = new java.util.Date();
try{
pout = new PrintWriter(new BufferedWriter(new FileWriter("Crawler_log"+getLogFileDate(new Date())+".txt", true)));
pout.write("**************** New Log File Created "+ getLogFileDate(new Date()) +"****************");
pout.flush();
}catch (IOException e){
System.out.println("**********THERE WAS A CRITICAL ERROR GETTING TRACER SINGLETON INITIALIZED. APPLICATION WILL STOP EXECUTION. ******* ");
public static void main(String[] argz){
System.out.println("main method starts ");
Tracer tt = Tracer.getTracerInstance();
System.out.println("main method successfully gets Tracer instance tt. "+ tt.toString());
//the next method is where it fails - on pout.write() of log method. Why ?
tt.log(1, "HIGH PRIORITY");
System.out.println("main method ends ");
//private static reference
private static Tracer tracerInstance = new Tracer();
private static Date date = null;
private static PrintWriter pout = null;
public static DateFormat df = null;
}

In general I'd guess that a small, custom thing will be faster than a large, generic thing with a lot of options. That is, unless the writer of the small program have done something stupid, og the writer of the large program have done something very smart.
One problem with java in this respect is that it is next to impossible to judge exactly how much machine-level processing a single java statement takes. Things like JIT compilers makes it even harder.
In the end, there is really only one way to find out: Test it.

Proxy log format

Just looking for opinions on what everyone is using for log formating.
We are looking at log analysis tools and some require different log formats.
We are currently using extended2 log format.
TIA.
joe.

Extended2 seems to be a popular format. Quite a lot of people seem to use the default
format plus a few useful parameters like "cache finish status", etc, added.

WL5.1 Log format config

Is there a way to control the format of weblogic's logging?
I'm logging to Weblogic's log using Java code that looks something like:
T3Services.getT3Services().log().log( "Foo..." );
This results in log messages that look something like:
Wed Jan 17 15:57:03 CST 2001:<I> <T3Services> Foo...
I'd like to be able to modify, replace or even suppress the date, time, <I> and/or <T3Services>.
For example, my log subsystem is capable of generating the following message which I'd prefer to send to WL's log:
01-17-2001 15:57:03 <TRACE> <GUI> Foo...
Does WL5.1 support the level of log format customization I'm looking for, and if so where can I find information about configuring the logging format?

Owen Horne <[email protected]> wrote in message
news:3a663105$[email protected]..
>
Is there a way to control the format of weblogic's logging?No. The format of the logfiles is fixed in 5.1 and 6.0 release.
>
I'm logging to Weblogic's log using Java code that looks something like:
T3Services.getT3Services().log().log( "Foo..." );
This results in log messages that look something like:
Wed Jan 17 15:57:03 CST 2001:<I> <T3Services> Foo...
I'd like to be able to modify, replace or even suppress the date, time,<I> and/or <T3Services>.
>
For example, my log subsystem is capable of generating the followingmessage which I'd prefer to send to WL's log:
01-17-2001 15:57:03 <TRACE> <GUI> Foo...
Does WL5.1 support the level of log format customization I'm looking for,and if so where can I find information about configuring the logging format?

Deleting default trace file in java

Hello all,
Whats the best way to automatically delete default trace file in java instance? I want to delete these files lets say every week or 2 wkkds,Is there any type of configuration that can be done through NWA or OS...? or do i have to write some scripts? Please advice.

Perfect.
When set to 10, 0 -->9 are cyclic files. Regarding archiving, yes this is possible. Apart from defaulttrace files you can also archive other java log files (system, network,security etc). The configuration procedure is explained :-
http://help.sap.com/saphelp_nw04/helpdata/en/48/2edfd5bd3e0d4a81b90325fe195a70/frameset.htm
Once the 10th trace file(i.e.defaultrace9) is full, all the trace files (from defaulttrace0-defaultrace9) are zipped to a single file. The file compression ratio is extremely good.
Unfortunately there is no automated mechanism to clear off the archived files. This needs manual intervention(regular cleanup, script etc).
The archived log files may also be viewed for analysis from NWA.
While estimating the size for each defaulttrace consider three factors i) System load ii) Number of defaulttrace files.
iii) Retention days(without archiving)
Ex: System load as observed :
Say the trace file size is 10MB and 6 trace files get written in 4 hours of peak time and 1 trace files is written for 4 hours during non-peak time .Assuming 8 hours of peak business hours and rest all non-working hours.
No of files generated is 62 + 14 = 16 files of 10 MB each are generated per week day
If the defaulttrace file count is set to 16, you can retain one days' logs . Say you wish to retain the same with less number of files (i.e. 8) you would have to increase the file size to 20 MB. Also will have to look at file system space availability.
CAUTION: For a file system occupancy estimate, you will have to also consider as to how many Server nodes are
configured as each node has its own log area !
For this you need to observe the pattern as to how many files are being written then estimate the size and count
cheers !
PRADi

Logging Format like in default trace

Similar Messages

Maybe you are looking for