Kbase 18888: Apptivity Runtime Process Logging Levels
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/03/2003 |
|
Status: Unverified
FACT(s) (Environment):
Apptivity
SYMPTOM(s):
Apptivity processes are configured by setting Java properties. These properties are defined in properties files; for server processes (Component Manager, Distribution Manager, and Proxy Manager), these properties can also be entered on the command line.
For Apptivity server processes, the properties file is set by the command line parameter:
-Dapptivity.properties.file=<filename>
For the Application Client (project), the properties file is:
<project>.properties
In each of these properties files, the logging level can be set via
the apptivity.log.level property.
Some guidelines for the usage of various logging levels follow.
apptivity.log.level=0
---------------------
This will give no information unless errors are generated. This would
be good for a deployment environment where everything is running
smoothly and you only want to detect errors.
apptivity.log.level=1
---------------------
This will give minimum information, mostly logging connections and
disconnection among server components and clients. It is useful when
you want to make sure that the different server components are talking
to each other or if you want to see which Component Manager a client
is connecting to.
apptivity.log.level=2 - 255
---------------------------
Increasing levels of verbosity of traffic between components.
The apptivity.log.file property can be used to redirect the logging
information to a file