How Log X-Ray works

Attach the debug log (required). Add the ER Extract and the PAR of the same object for readable rule text and checks. Nothing leaves your browser.

The log prints Line(S8:22), a section and a line number. The tool lays those lines over the extract, compares the text as a check, and shows what ran, which branches were taken, table I/O and every business function parameter.

Loops are collapsed to one row per statement with run count and total time. See Hot spots & loops. Click a line to see when it ran, with the log\u2019s own timestamp and line numbers. For a loop, step through every pass and see the value of each pass. If a line reads differently in the log than in the extract, it is flagged: the extract may have been exported after a change.

Logs over 256 MB are read in chunks and only the event rule trace lines are kept.

JD Edwards EnterpriseOneLog X-Ray

Reads a JD Edwards debug log together with the ER Extract and the .par of the same object, and lays what happened at run time over the event rules: which lines ran, which branches were taken, the table I/O and the business function calls with every parameter. Serverless: your files stay in your browser.

Attach the debug log, ER extract and PAR .log.txt.par
Reads three kinds of input: the debug log (jdedebug.log or the UBE log), the ER Extract .txt, and the .par export. Nothing leaves the browser. Log X-Ray v2.0.0