Chapter 5: Workbench diagnostic information
To help solve operational problems of a Workbench, diagnostic information is available. You can find
information through:
• Client tracing
• Workbench log file
Client Tracing
You can start client tracing in these ways:
• Press <Shift><l> (capital letter 'L'), messages and events in the browser and at the UI server are
captured in a trace file. A new browser window is created that shows a button to download the trace
file. After download, the captured events can be examined off-line.
• Select Options > Activate trace mode to start the LN UI trace mode. Then start the Workbench.
The Workbench will automatically start capturing messages and events in a trace file, as described
earlier. This will show the browser window to download the trace file.
Workbench Log File
Each Workbench web application generates a log file with message and logic events at the UI server
side of the Workbench. The messages, with increasing degrees of verbosity, can have the severity
ERROR, INFO or DEBUG.
The name of the Workbench log file contains the session code and version, release and customer of
the corresponding 3GL session. For example; tdpur8360m000_B60_a_sy82.txt.
When the Tomcat web server is used, the file can be found in this folder:
${catalina.base}/logs
When the JBoss web server is used, the file can be found in this folder:
${jboss.server.log.dir}
For web servers other than Tomcat or JBoss, the file is stored in this folder:
${java.io.tmpdir}
To find the value of:
• ${catalina.base}
• ${jboss.server.log.dir}
• ${java.io.tmpdir}
Infor LN HTML5 Workbench Administration Guide | 24
Workbench diagnostic information
To Next Page
Loading...