The Debugging section of the admin console at Debugging > Debugging can be found by following. Debugging > Debugging. This section of the console controls debugging options as well as the execution of Java scripts.
...
For small operations, the table of activities is usually empty at any instant in time. If you need to create an ongoing activity for testing purposes, you can import a large group of records, or schedule a mass edit or mass delete action.
Show Database Statistics
This monitoring tool makes it easy to monitor SQL queries and find potential areas to optimize, such as inefficient searches or missing indexes. To use it, click Show database statistics. This tool shows the 100 slowest-running queries, where the average time is more than 10 milliseconds.
You can show database statistics for all KBs on the server, or run it on a selected KB.
Start or Stop Debugging
Standard server logs contain many standard output messages like Info, Warning, or Errors. When debugging starts, the server outputs more messages, prepended with Debug. In most cases, the standard server outputs are enough to identify issues that arise. Debugging is useful only if standard server outputs do not give the cause of the problem.
...
The Bean Shell button brings up a separate window to run Java scripts for testing and debugging purposes. From this window, the admin gains full control over the Java Virtual Machine (JVM) that runs the
systemCompanyname
system.
| Note |
|---|
To run scripts in Bean Shell, you must log in to the target server using SSH. In the Script section of the Admin Console, open the Token section and follow the directions to generate and apply the access token. You can then run scripts from the Admin Console until the token expires. Tokens last for ten minutes. |
Bean Shell debugging allows runtime manipulations of parameters and instrumentation. For example, if the admin knows a specific class name, the class may be instantiated, and all of its methods may be invoked from this window.
...