Messages are logged throughout the processing of runtime activity. These messages are logged by a logging thread that manages access to the log file. The log file is a plain text file called NNSYMessageLog.nml. This file can grow without bounds even though the log file is automatically archived daily, the user to consider log size if full logging is configured to log numerous levels of severity.
The level of logging information is determined by the 'Engine Logging Level' and 'Services Log File Logging Level' parameters in the runtime instance configuration properties. (See Runtime Instance Configuration Properties) The levels on a scale from the highest number of log messages to the lowest number of messages are DEBUG, INFO, AUDIT, WARN, ENGR, and CRITICAL. DEBUG and INFO levels are designed for use during initial testing and debugging of processes. After a package of one or more business processes is running in a production environment, the logging level should be set to WARN. An explanation of each severity level and types of messages produced with each level are provided below.
When the runtime engine encounters a critical error, it logs the error and terminates the business process that is in error. You can examine the log file to determine what happened. If it is a problem (such as a full queue or exceeding the database storage), you can correct the problem and continue the engine using the Command and Control interface. If you cannot correct the problem dynamically, you need to shut down the engine, fix the problem, and restart the engine.
You can view instance logs using the Show Instance Log option available for each runtime instance in the Server Explorer.
Example
The following is an example of an entry from the NNSYMessageLog.nml file showing a business process being initialized:
2003-02-12 00:33:44.525
PSEngine.exe|6088|3768||PS|EVENT_CAPTURED|Info|
Capture|The Event1 event (101006) was captured.
.
.
2003-02-12 16:25:36.369| PSEngine.exe|6088|3768|PS|PROCESS_IN_ERROR|Error|
Analysis|The Process PerfSQL (94002) is now in error state.
The seventh field in the logged information indicates the severity of the message. There are six levels of message severity:
|
Level |
Description |
|
DEBUG |
All levels of severity are logged. |
|
INFO |
Most levels of severity are logged. The message contains information about each step in the processing (default). |
|
AUDIT |
Audit, warning, engineering, and critical messages are logged for this level. The message is informational and represents significant information that should be placed in an audit trail. |
|
WARNING |
Warning, engineering, and critical messages are logged for this level. The message is a warning only. |
|
ENGR |
Engineering and critical messages are logged for this level. The engineering message is an error message identifying a potentially serious problem or an unexpected condition. |
|
CRITICAL |
Only critical messages are logged for this level. The message is an error message identifying a critical and fatal problem. The engine shuts down. |
See Message Log Contents for a description log contents and log archiving.