Goal: This bulletin document is a central repository of all possible logging in EnterpriseOne
Reference:
JD Edwards EnterpriseOne Logging Matrix: Activating, Creating and Retrieving the Correct Logs (Doc ID 1332681.1)
How to turn on logging in WebDev client
Goal
Through this demonstration, you are familiar with components of single objects
Understand the parameters in JDE.INI and JAS.INI
Understand Environment which is made up of Path code and OCM mapping
Parameters which is related to logging
JDE.ini
[DEBUG]
Output=FILE
LEVEL=BSFN,EVENTS
DebugFile=c:\logs\jdedebug.log
JobFile=c:\logs\jde.log
OWDEVELOPER=TRUE
[UBE]
UBEDebugLevel=6
UBESaveLogFile=1
Output: (default) NONE
NONE: to not capture jdedebug.log
FILE: trace as defined in (debugging) LEVEL
LEVEL: this determines the level of detail. This definition is important to understand how an object is made up of or we define it in EnterpriseOne
In the IT industry, an object is made up of C functions and specification. So BSFN represents all C Components in E1 and EVENTS represents specification (which can be called in many different names depending on its location and usage). Refer to E1: ENV: Overview of Specifications (SPEC) in EnterpriseOne (Doc ID 1)
DebugFile and JobFile determines where to store the output
UBEDebugLevel is determined the level of detail of the batch job. Set this value 6 unless different settings are a requirement by development
UBESaveLogFile 1 for TRUE
JAS.INI
a. Jdedebug.properies (at C:\E910\system\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF)
# In H4Apps environment we should have atleast one log turned on
# to make sure all logs above warn should get into the
#
# FILE = <Set the location of the logfile to output the logs>
# LEVEL = <Should be either SEVERE or WARN or APP or DEBUG>
# <Log levels priority is SEVERE > WARN > APP > DEBUG >
# <Default setting in H4Apps is APP>
# FORMAT= <In Production format should be APPS>
# <Formats> APPS, TOOLS, TOOLS_THREAD
# MAXFILESIZE = <The maximum file size of the log file>
# MAXBACKUPINDEX = <Maximum number of backups that need to be maintained>
# COMPONENTS= <The components that needs to be logged in the file>
To configure and enable user-specific jasdebug.log:
à Click on “Create New User Specific Log Configuration” (Push button).
Enter User Name, the User Name entered is same with E1 Login ID
Click “OK” and “Apply”
Note: Must click “APPLY” to make any change
Log Level = “Application Level Activity”
Note that Append Log File is set “False” (not to attach on E1root.log)
Now you have configued user based jasdebug log files.
Login E1 by using this user id and conduct application activities through web client ……
How to view the captured user-specific jasdebug log
- Go to Instance you are working on (for example, OAS8129710)
- Find that user-specific jasdebug.log is being captured with user configured log file.
- Click on the log file to view.
- Clieck “Download Entire Log File” to retrieve and save the full log file.
To turn off user-specific jas logging.
(Check Box) Select – select the user-specific log
(Push button) Delete – delete the seleted user-specific log
(Push button) Apply – update the change the to system.
Capturing user related CallObjectKernel on Enterprise Server
Signed on E1 using your E1 User ID
Within Server Manager, click “Management Dashboard”
- From pull-down menu from below screen, choose “Search for User Resources”
- Enter your E1 User ID and click Search
(continue..)
Find there are two different logs under your loggin ID:
one from JAS
the other from Enterprise Server
To view JAS log, click Logs Files under HTML Server Session.
There is another session for “Enterprise Server Resources”
Note the Process ID for Process Name “Call Object Kernel” which is 11940 in this demo.
Click this specific Process ID suhc as 11940.
Process ID: 11940 properties are set as below
(continue..)
To turn on logging tick (check box) Enable JDEDEBUG.LOG, and click Save.
Run E1 application through web client…
As it was defined from the specific Process ID (process ID = 11940 for this demo) jdedebug.log will be found as below from the same place as highlighted before.
Click “view” to check/capture jdedebug.log
To save jdedebug.log click “Download Entire Log File”.
Important!!! At the end of logging, please remember to turn it off.
How to turn on logging for UBE/Batch Job
Goal
You can turn on UBE log dynamically
Understand the logs in the server is the best ones which combine both UBE kernel and Call Object kernel
Practice
Log on to any environment (we are going to submit a job to the server so either J* or non-J* environment the outcome will be the same)
Enter batch application ID and press find button
Highlight version you want to submit and click Select
(Form Exit) Advanced
Set UBE Logging Level = 6
Tick Data Selection to set proper data selection
Set Data Selection
Click OK on the Printer Selection screen
(to retrieve log captured)
On Work with Batch Versions screen, (form exit) Submitted Jobs
Look for the job you have submitted then (Row Exit) View logs
Tick both Logging and Tracing then click OK to save
Save it
How to turn on logging for the batch job which is called by an interactive application
Assumption: the issue is happening in Live environment so it is not applicable to modify JDE.INI in server
Business scenario: The Print Check did not update status correctly
Exercise
Modify jde.ini and jas.ini as guided at “C. How to turn on logging in WebDev client”
Log on to WebDev client with user ID/Password LOCAL/LOCAL
Start Local web
Go to the interactive application which calls UBE(s)
Verify logs traces by this action (5 different logs are to be generated)
log
log
UBE logs
log
E1root_*.log
Turn on logging through serveradministrationworkbench.exe
Goal
You are able to configure server activities
You are able to capture different types of kernels through conventional SAW
Exercise
Launch serveradministrationworkbench (SAW)
START > Run (type in) serveraministrationworkbench.exe
Or, launch it through Windows Explorer
Log on using your user ID or JDE/JDE
Select tab “Query”
Click Add
Enter machine name of the logic server with port number
Click View users to find user specific Call Object kernel Process ID
Click Processes
Right mouse button click then click Turn on Server Logging
To view logs click View Debug Log and View JDE.log
What information is written at logs
To be added ...
log:
this log contains system level error (which are related with tools release. In other words, any component which belongs to the system)
This include ODBC, connection, kernel level error
log: since business functions in E1 must be called through API CallObject () so we call it as Call Object Kernel log. So this file traces all business functions flow. Exception: E1: BSFN: Frequently Asked Questions on Business Functions / Methods Running on JAS (Doc ID 1090584.1)
E1root_*.log: this file contains system level error in JAS (java application server) depending on the level you have set from jdedebug.properties file or server manager
log: this file traces all specification as we defined in jdedebug.properties file.
