Engine trace
| Administration Page | Application Contract | Syracuse Collaboration | Application Class | Syracuse x3SessionConfigs | Representation | x3SessionConfig (in $edit facet only) |
|---|
This page is intended to set up logs on the Sage X3 server associated with the current connection. It is transmitted to all the connections opened on the corresponding endpoint from the current session (for Classic pages as well as query/detail/edit ERP pages).
When this page is opened, the following information can be entered:
This check box must be selected when a log is to be generated by the SAFE X3 engine.
This information is displayed and modifiable only if the previous check box is selected. This field is a numeric value type that is the addition of different numeric values (power of 2) corresponding to the elements that must be logged:
| Value | Element logged |
| 1 | Only the execution of the Gosub, Call, Callmet, and Fmet engine instructions. |
| 2 | Execution of all engine instructions. |
| 4 | Execution of the Read or For statements when they are used to access the database. |
| 8 | Technical data feed exchanged between the SAFE X3 engine and the database driver (sadora or sadoss query). |
| 16 | Technical JSON data feeds between the client and the web server. |
| 32 | Technical binary data feeds between the web server and the Sage X3 server for Classic pages. |
| 64 | Technical exchanges between the LDAP server and the Sage X3 server. |
| 128 | Only the execution of the Opldap instruction (Technical). |
| 256 | Technical exchanges linked to the runtime starting phase. (Technical) |
Defines the directory where the log files are generated on the Sage X3 server. The directory is relative to the folder directory on the process server. Make sure that the sandbox configuration allows you to write in this directory.
Defines the endpoint (the Sage X3 folder) in which the log is set.
The setup is updated when the Submit link is launched.
This function triggers the log mode for the X3 engine. This mode is global, and will be applicable to all the sessions (V7 like or classic) started after the log activation. Take care that using this mode is consuming additional CPU, memory and disk resources. This should be done only for a short period of time for debugging, profiling and optimisation purposes.
This function stops the log mode previously enabled. It doesn't stop the log for the running sessions, but the new sessions started will no more fill the log.