When testing an ePortal presentation project before it is staged on the ClearPath server, errors, trace messages, and user data transferred to the peer application can be logged using the following procedure.
In Solution Explorer, click on the appropriate ePortal presentation project node.
On the Tools menu, click ClearPath ePortal Log Options, and click Log Properties.
In the Log Level box, select one of the following levels that is appropriate for the debugging task.
| Log Level | Description |
|---|---|
| Level 0 - None | No entries are written to the Windows event viewer or the trace file. This level is not recommended. |
| Level 1 - Error | Only errors are written to the Windows event viewer and trace file. The current operation cannot continue with errors. |
| Level 2 - Warning | Only errors and warning messages are written to the Windows event viewer and trace file. The current operation continues, with warnings. |
| Level 3 - Informational | Only errors and warning messages are written to the Windows event viewer and trace file. Informational messages are written to the trace file. |
| Level 4 - Verbose | Only errors and warning messages are written to the Windows event viewer and trace file. Informational messages are written to the trace file. Detailed trace messages, including data buffers, are also written to the trace file. User buffer traces are written to the Debug Output Window. |
(Optional) Clear the Event Threshold Enabled check box if you want to disable the suspension of an event logging operation. The check box is enabled by default.
If the option is enabled, the event logging operation will be suspended when the rate of events generated by the application reaches a specified threshold. The event logging operation resumes when the rate falls below the threshold.
(Optional) Enter a value in the Event Threshold field. It indicates the number of events per minute (moving average) that triggers suspension of event logging. The default value is 10. The field is disabled if the Event Threshold Enabled check box is not selected.
Notes:
In order to write errors and warnings to the event viewer, you must start Visual Studio with administrator privileges. To do this, start Visual Studio by right-clicking the icon or executable and selecting Run as Administrator. If you do not run Visual Studio as an administrator, then messages are still written to the trace file.
When testing under the Visual Studio debugger, trace files are written to a folder on your development system. By default, the files are located in the local AppData folder for the particular user. To access the files, navigate to the folder %LOCALAPPDATA%\Unisys\epDeveloper\Logs using File Explorer.
To understand the message obtained in the log file, refer to the following example:
EPINT Information: 0 : 06/17 05:12:09.539 105
where,
EPINT is a specified name used for Trace source for messages for ePortal. (Separate Trace source for messages are created to prevent the default display of Trace Write messages in the Visual Studio output window when running locally.)
Information is the logged level of the trace entry. Apart from Information, it can also have a value of Error, Warning, or Verbose.
0 is a placeholder for trace write messages.
105 is the Thread ID.
Prefixes such as time, thread ID and message type are added for tracing the message.
For information about how to write your own messages to the log from code you wrote, refer to Logging Messages from your Code.
For information about how to log the messages from orchestration, refer to Logging from your Orchestration.
Log messages written to the event viewer or to the trace file can be gathered for analysis by Unisys support personnel. Refer to Gathering Diagnostic Information for more information.
The ClearPath ePortal Manager Help describes how to gather diagnostics after a presentation project is deployed. Log messages are included when diagnostics are gathered.