Our enterprise-app setup is a bit different, but we configure log4j per WLS
server instance. A JMS queue then serves as the logging destination for
that server.
In the start-up script (startWebLogic.sh) we add the -Dlog4j.configuration=?
to the start command, where ? points to the config for that server instance.
|-----Original Message-----
|From: Patrice Thiebaud [mailto:[EMAIL PROTECTED]]
|Sent: Tuesday, September 03, 2002 7:46 AM
|To: [EMAIL PROTECTED]
|Subject: Scope of logging in an application server
|
|
|I did the necessary to configure the use of log4j in a WLS
|enterprise
|application, using a specific configuration file and
|specific log file name(s).
|My assumption is that the preferred approach is to have
|separate logging
|for each deployed enterprise application and/or
|stand-alone component.
|
|I would like to know what approaches are generally used in
|an application
|server environment.
|
|Thanks in advance.
|
|--------------------------------------------------------------
|Patrice Thiebaud - Presales Senior Consultant
|BEA Systems - France
|Tour Manhattan
|6 place de l'Iris
|92095 PARIS La Défense Cédex
|Tel: 33 1 41 45 70 27 Mobile: 06 08 05 95 95
|--------------------------------------------------------------
|
|
|
|
|--
|To unsubscribe, e-mail:
|<mailto:[EMAIL PROTECTED]>
|For additional commands, e-mail:
|<mailto:[EMAIL PROTECTED]>
|
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
