Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Logging Approach

 
Siyaram Singh
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are evaluating our existing application 's logging approch.
Application use WAS 4.0.X , Log4J logging framework, and J2EE (without EJB).
I think log4J is meant only for java applications, not for Application Server, Network Failure and etc.

How we should proceed to evaluate /monitor application server logging approch and ETC.......

Thanks,
SS
 
jason white
Ranch Hand
Posts: 60
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Siyaram,

In this situation I typically rely on the Application Servers' logging mechanism. I realize you might have already considered this but I figured I would mention it.

You can also monitor web service endpoints via a tool like AmberPoint etc..

You can also access jvm statistics via custom code...

-jason
 
Marie Pierre Courbevoie
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Siyaram

Enable and configure the "Trace Service" from your administrative console, usually log files are located in the logs directory of your server installation.By default, the server is configured with: "all=disabled"
Steps from the administrative console:
1/Trace Service
Enable trace string
2/Click edit
Select what you want from the displayed list (if you're interested by the server behaviour, all server services are displayed)
Select the trace level: Debug, Entry/Exit, Event
.......
.......

Regards

Marie Pierre
[ August 13, 2005: Message edited by: Marie Pierre Courbevoie ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic