This chapter contains the following topic:
The logging utility in the dynamic Java connector, the Java connector, and Java connector Architecture (JCA) is built on top of Apache Open Source Project Log4j. The jdelog.properties file defines the settings for the logging configuration. The jdelog.properties file should be physically located in CLASSPATH.
The jdelog.properties File consists of three log files:
[E1LOG]
[LOG1]
[LOG2]
The following table provides a description of the parameters in each of the log files:
| Parameter | Description |
|---|---|
| FILE | Set this value to the location of the log file. |
| LEVEL | Set this value to one of the following:
Note: The levels are listed above in the order of their priority, with SEVERE being the highest priority and DEBUG being the lowest priority. The default setting is APP. |
| FORMAT | Set this value to one of the following:
Note: In a Production environment, the FORMAT parameter should be set to APPS. |
| MAXFILESIZE | Set this value to the maximum file size of the log file. The default setting is 10MB. System performance can be affected if this value is set too high. |
| MAXBACKUPINDEX | Set this value to the maximum number of backups that need to be maintained. The default value is 20. System performance can be affected if this value is set too high. |
| COMPONENTS | Identify the components that need to be logged in the file. Components that you might use with a Java connector for interoperability include: JDBC, RUNTIME, INTEROP, JDBJ, EVENTPROCESSOR. |
The Tools Reference and HTML Web Server Reference guides provide information for creating and managing jdelog.properties files.
See JD Edwards EnterpriseOne Tools Release Tools Reference Guide.
See JD Edwards EnterpriseOne Tools Release HTML Web Server Reference Guide.
This is the section name for the root log. The following sample configuration logs all SEVERE and WARN messages to the jderoot.log file on the C drive.
[E1LOG]
FILE=C:\\ConnectorEventsClient\\log\\jderoot.log LEVEL=WARN FORMAT=APPS MAXFILESIZE=10MB MAXBACKUPINDEX=20 COMPONENT=ALL APPEND=TRUE
Logging RUNTIME and INTEROP components at the APP level is helpful for application developers. Application developers can use this log to analyze the flow of events in the web client. The following sample configuration logs all SEVERE, WARN, and APP messages to the jas.log file on the C drive.
[LOG1]
FILE=C:\\ConnectorEventsClient\\log\\jas.log LEVEL=APP FORMAT=APPS MAXFILESIZE=10MBMAXBACKUPINDEX=20 COMPONENT=RUNTIME | INTEROP | JDBJ APPEND=TRUE
Logging RUNTIME and INTEROP components at the DEBUG level is helpful for tools developers. Tools developers can use this log to debug tool level issues.
[LOG2]
FILE=C:\\ConnectorEventsClient\\log\\jasdebug.log LEVEL=DEBUG FORMAT=TOOLS_THREAD MAXFILESIZE=10MBMBMAXBACKUPINDEX=20 COMPONENT=RUNTIME | INTEROP | JDBJ APPEND=TRUE