JNDI Adapter Logging Capabilities
The logging capabilities available through the JNDI adapter are dependent on whether you are running the adapter in process or out of process. Log4j logging capabilities are used for adapter logging purpose.
General information about JNDI adapter logging can be found in the following sections. For additional information about logging, see the Property Administration help and
Info*Engine Implementation.
In-process Adapter Logging Capabilities
For in-process adapter configuration, log settings are controlled by the parent service where the adapter is being used (for example, the servlet engine or server). Depending on the parent service being used, the log messages are written to different log files. For more details about log4j logging settings of servlet engine or server, see
Info*Engine Implementation.
Out-of-process Adapter Logging Capabilities
When running the JNDI adapter out of process, the logging configuration for the adapter is determined by the log4j configuration you have provided for your adapter. The same set of loggers used by the Info*Engine process control the logging settings of your adapter, so all that is needed is to construct a new log4j configuration file and instruct your adapter to use it. The following steps explain how to construct a new log4j configuration file to do so:
1. Make a copy of the following file:
<Windchill>/codebase/WEB-INF/log4jIeServer.properties
2. Customize the log levels and appenders (including where you want log files created) and then pass a reference to this file (within your adapter CLASSPATH) to it on startup.
For more information on specifying the log4j configuration for your out-of-process adapter, see
Modifying the Start Files. For more information on log4j settings of the
Info*Engine processes, see
Info*Engine Implementation.