4/10/2021 Document 662082.

1
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

E1: UBE: How to Capture Report Interconnect Logs Without Using Server Manager (Doc ID
662082.1)

In this Document

Goal
Solution
References

APPLIES TO:

JD Edwards EnterpriseOne Tools - Version SP24 and later

Information in this document applies to any platform.

GOAL

Information Center: Overview of Universal Batch Engine in the JD Edwards EnterpriseOne Tools and Technology Product >
Information Center: Using Universal Batch Engine in the JD Edwards EnterpriseOne Tools and Technology Product > Note
1513115.2

When a UBE is called from Batch Versions it is possible to submit it with debug logging enabled and level set to '6'. But how
can I capture similar debug logs for UBEs submitted via Report Interconnect calls?

Note: Starting with tools release 8.97 there is a more effective way to capture these same logs using Server Manager.
Refer to Doc ID 955463.1 for more information.

SOLUTION

Interactive application calls a UBE and UBE calls a UBE, which runs on the server or locally, logs need to be turned on by way
of the JDE.INI. Logs cannot be turned on through Batch Versions.

If the UBE is running on the server, set the SERVER JDE.INI to the following:

[DEBUG]
OUTPUT = FILE

[UBE]
UBEDebugLevel=6
UBESaveLogFile=1

Note: This is a dynamic property, EnterpriseOne services do not need to be restarted.

Logs can be viewed from Work with Submitted Jobs. Highlight the job and select from the row exit, View Logs. Check the
boxes Logging (JDE.log) and Tracing (JDEDEBUG.log). This will pull the log up on the screen.

If the UBE is running locally, set the WORKSTATION JDE.INI to the following:

[DEBUG]
OUTPUT = FILE

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=kv9ntfkde_666&id=662082.1 1/2
4/10/2021 Document 662082.1
[UBE]
UBEDebugLevel=6
UBESaveLogFile=1

The jde.log and jdedebug.log will be located where the jde.ini has specified:
[DEBUG]
DebugFile=c:\jdedebug.log
JobFile=c:\jde.log

The UBE log will be located in the print queue directory.

Once testing of your UBE issues is done, turn off.

If you expect the log files to be large in size or if you notice any truncation of log files then it is suggested
that maxDebugFileSize and maxDebugBackupIndex settings are verified in the ini file.
Refer to Doc ID 1522056.1 E1: KER: How to Define the JDEDEBUG.LOG for a Large Log File Without Truncation.

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a
discussion in the Design Tools & Output Technologies - JDE1 Community.

To look at upcoming or archived Advisor Webcasts review Doc ID 1450327.1 Advisor Webcast JD Edwards EnterpriseOne
Schedule and Archived Recordings. If your topic is not currently scheduled suggest it.

REFERENCES

NOTE:1332681.1 - E1: JD Edwards EnterpriseOne Logging Matrix: Activating, Creating and Retrieving the Correct Logs
NOTE:955463.1 - E1: SVM: UBE: UBE Logging For A Report Called From An Application Or A Function Using Server Manager
NOTE:1450327.1 - Advisor Webcast JD Edwards EnterpriseOne Schedule and Archived Recordings
NOTE:626564.1 - E1: UBE: How to Generate Logging Information for a Report or Batch Application
NOTE:1522056.1 - E1: KER: How to Define the JDEDEBUG.LOG for a Large Log File Without Truncation
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=kv9ntfkde_666&id=662082.1 2/2