Logging for Interactive Application in Server Manager

APPLIES TO:

JD Edwards EnterpriseOne Tools - Version 8.97 and later
Information in this document applies to any platform.

PURPOSE

What are the steps to turn on and view logging from the Server Manager Management Console for a JAS log and Enterprise Server callobject kernel jdedebug log.

This knowledge document is designed to direct you through basic JDEdwards EnterpriseOne Server Manager Accessing / Debugging Logs and Changing/Creating Logging for Managed Instances functionality.
The knowledge attachments are not meant as a substitute for the Server Manager Guide, but as an aid for better understanding of the Server Manager Accessing Logs and Changing/Creating Logging for Managed Instances processes.

For 9.1 Server Manager Guide, refer to JD Edwards EnterpriseOne Installation and Upgrade Documentation Release 9.1 - Installation tab.

SCOPE

For customers using Server Manager with Tools Release level 8.97 or higher.

DETAILS

How To Turn On Logging For Interactive Applications In Server Manager

These are the steps to turn on logging for JAS and Enterprise Server Call Object kernel jdedebug with the Server Manager tool.

Log into Server Manager

Turn on JAS log

1. From Dashboard - Managed Homes, Managed Instances choose the EnterpriseOne HTML Server;
2. From Configuration box on the left side choose jdelog.properties or Logging;
3. From user Specific Log File Configuration click button Create New User Specific Log Configuration;
4. Enter the User ID in the User Name and click OK;
5. Click Apply.

Turn on Enterprise Server Debug log

1. From Dashboard - Managed Homes, Managed Instances choose the EnterpriseOne HTML Server (necessary to start at HTML server to gather information);
2. From Runtime Metrics choose User Sessions;
3. Find the user logged in and note the PID number in the column Remote Environments.;
4. From Dashboard - Managed Homes, Managed Instances choose the EnterpriseOne Enterprise Server;
5. From Runtime Metrics choose Process Detail (Note if Runtime Metrics isn't available, refer to Document 1270213.1);
6. Find the Call Object Kernel with the noted PID number and click on the "CALL OBJECT KERNEL" hyperlink in the Process Name column;
7. From Log File Configuration click Enable JDEDEBUG.LOG;
8. Click Save.

Retrieve Enterprise Server Debug log

1. Within the Log File Configuration click View for JDE.LOG;
2. This will start a new Log File Viewer window. Click hyperlink Download Entire Log File;
3. Save the jde_xxxx.log;
4. Click X to close the Log File Viewer window;
5. Within the Log File Configuration click View for JDEDEBUG.LOG;
6. This will start a new Log File Viewer window.  Click hyperlink Download Entire Log File;
7. Save the jdedebug_xxxx.log;
8. Click X to close the Log File Viewer window.

Turn off Enterprise Server Debug log

1. De-select Enable JDEDEBUG.LOG;
2. Click Save.

Retrieve JAS log

1. Click on Management Dashboard;
2. From Select Instance drop-down choose the EnterpriseOne HTML Server;
3. From the Available Log Files choose the userID_userID_todaysdate.log;
4. Click hyperlink Download Entire Log File;
5. Save the userID_userID_todaysdate.log.

Turn off JAS log

1. Click on Management Dashboard;
2. From Select Instance drop-down choose the EnterpriseOne HTML Server;
3. From Configuration box on the left side choose jdelog.properties or Logging;
4. From user Specific Log File Configuration select the added Log Name and click the button Delete, Click OK to confirm, click the Apply button.

It is not possible to clear the logs from Server Manager.  If the Enterprise Server Debug log is large or another test is needed then go to the path where Enterprise Server is installed and clear (not delete) the log from there.   If the jdedebug log file is deleted, it will not be recreated.