Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
docs:2000_concepts:0800_data_processing:0300_execution_log [2022/08/25 00:00] – ↷ Page moved from 2000_concepts:0800_data_processing:0300_execution_log to docs:2000_concepts:0800_data_processing:0300_execution_log administratordocs:2000_concepts:0800_data_processing:0300_execution_log [2025/06/12 03:58] (current) – Change to AwareIM aware_support3
Line 3: Line 3:
  
  
-The results of rule evaluation and action execution are written into the //execution log//. This log can be very useful when checking whether business rules behave as expected (especially when testing new configuration – see [[2000_concepts:1000_config_proc:0300_testing_mode|Testing Mode]]). +The results of rule evaluation and action execution are written into the //execution log//. This log can be very useful when checking whether business rules behave as expected (especially when testing new configuration – see [[docs:2000_concepts:1000_config_proc:0300_testing_mode|Testing Mode]]). 
  
 The log record consists of the record timestamp, the name of the business space in which the user that has issued the request operates and the name of the user. For example, The log record consists of the record timestamp, the name of the business space in which the user that has issued the request operates and the name of the user. For example,
Line 26: Line 26:
 ===== All server events including SQL===== ===== All server events including SQL=====
  
-This is the most verbose level. This is the same as the previous level, but the rule log also includes records of all SQL commands that //**Aware IM**// sends to the database.+This is the most verbose level. This is the same as the previous level, but the rule log also includes records of all SQL commands that //**AwareIM**// sends to the database.
  
-The levels may be set up using the [[7000_glossary:control_panel|Aware IM Control Panel]] (Settings/Logging menu item) or in the ''logger.props'' file located in the ''BIN'' directory of the //**Aware IM**// Server installation. +The levels may be set up using the [[glossary:control_panel|AwareIM Control Panel]] (Settings/Logging menu item) or in the ''logger.props'' file located in the ''BIN'' directory of the //**AwareIM**// Server installation. 
  
 When you run the Settings/Logging command you can also specify whether the system will log any events into a log file or not. If you tick the corresponding checkbox the system will store events of all applications running in the production mode in the file ''AwareIM/bin/main.log'', and it will store events of all applications running in the testing mode in the file ''AwareIM/bin/test.log'' When you run the Settings/Logging command you can also specify whether the system will log any events into a log file or not. If you tick the corresponding checkbox the system will store events of all applications running in the production mode in the file ''AwareIM/bin/main.log'', and it will store events of all applications running in the testing mode in the file ''AwareIM/bin/test.log''
Line 34: Line 34:
 ====== Log Viewer ====== ====== Log Viewer ======
  
-The execution log may be viewed using the [[7000_glossary:control_panel|Aware IM Control Panel]]. There are several menu items that can view the log:+The execution log may be viewed using the [[glossary:control_panel|AwareIM Control Panel]]. There are several menu items that can view the log:
  
   - View/Production Log menu item – opens the current log for all applications running in the production mode   - View/Production Log menu item – opens the current log for all applications running in the production mode
   - View/Testing Log menu item – opens the current log for all applications running in the testing mode   - View/Testing Log menu item – opens the current log for all applications running in the testing mode
   - File/Open Log File – opens the specified log file   - File/Open Log File – opens the specified log file
-//**Aware IM**// displays the log as a tree structure where every node represents a single log record. The nodes of the tree are hierarchical – for example, all log records spawned by an external request (such as a request to start a process or update an instance of a business object) are children of the node representing the external request. This is illustrated on the picture below:+//**AwareIM**// displays the log as a tree structure where every node represents a single log record. The nodes of the tree are hierarchical – for example, all log records spawned by an external request (such as a request to start a process or update an instance of a business object) are children of the node representing the external request. This is illustrated on the picture below:
  
-{{ documentation:images:execution_log_output.png?nolink&600 |}}+{{ docs:images:execution_log_output.png?nolink&600 |}}
  
 The picture shows execution of the DeleteTopic process – the corresponding nodes are expanded to show all details of the log. Note also that the Log Viewer shows different types of log records with different icons and colors. Using the Log Viewer one can quickly browse through the log and delve into the details of a particular request only when necessary. The picture shows execution of the DeleteTopic process – the corresponding nodes are expanded to show all details of the log. Note also that the Log Viewer shows different types of log records with different icons and colors. Using the Log Viewer one can quickly browse through the log and delve into the details of a particular request only when necessary.
  • Last modified: 2022/09/13 18:07