Configuring Synapta Services Builder for Screens Event Logging
When you configure event logging, you can view events, track session management and task execution in the runtime system, and troubleshoot any problems that might occur. All events that are logged to MCS have a unique event code and a summary message, which includes the nature of the event, pool name, and, if applicable, the session ID and task name. For the complete list of codes, see Event Logging Codes.
You can log errors, warnings, and information for all system events. Along with runtime system events, you can also log user-defined and client-requested events, including each event's associated screen and task data.
|To configure event logging options for Synapta Services Builder for Screens
- In the MCS left pane, point to Products and then click Services Builder for Screens.
- From the Services Builder for Screens tree in the MCS left pane, expand the Servers tree, expand your run-time server, then choose Configure.
- From the Configure, System page, under Select Item to Configure, double-click Log.
To turn off logging to MCS, clear the options in this dialog box.
- Select the events you want to log.
|Log all Errors
||All Error events are logged. These include: Unrecognized Screens, Host Response Timeouts, plus other problems that may cause navigation to end in an error, session creation errors, and other session management events.
|Log all Warnings
||All Warning events are logged. These include: Missed Transients (if a transient screen was recorded, but not encountered, and navigation continued) or Session Disconnected (if the host disconnect occurs during navigation).
|Log all Information
||All other events are logged. These include: Beginning and ending navigation cycles, (including table navigation), on Next Step or Step Transitions, and when sessions are created, allocated, un-allocated, and destroyed.
- For each selected event type, select the type of data you want included in the log.
||A copy of the screen associated with the event is displayed in the Event Raw Data window. You can choose to have this data displayed for each event-type: errors, warnings, and information. If an event does not have screen data associated with it; no screen data will be displayed, regardless of whether this option is selected.
||Task inputs and outputs, including task step inputs for the event is displayed in the Event Message window. You can choose to have this data displayed for each event-type: errors, warnings, and information. If an event does not have task data associated with it; no task data will be displayed, regardless of whether this option is selected.
- To send events to another log location, select the Log Events to Console or Service Log check box.
|If your Runtime Service is running
|In application mode
||Events are displayed in the run-time console.
|As a Windows Service
||Events will be added to install_directory\EAI\ScreenConnectors\servicelog.txt
|As a UNIX daemon
||Events will be added to install_directory/ScreenConnectors/log/runtime.log
- Click OK.
User-Defined Event Logging
You can enhance your logging capabilities by creating user events on task steps in Task Builder. If a particular task step has a user event defined for it, then that event will be triggered every time the task step is encountered in a task execution and the event will be logged to MCS. There are two properties associated with user event logging; Log User Event and User Event Message. For more information on the Log User Event and User Event Message properties, see Task and Task Step Property Descriptions.