8.7 Simulation of Automatic Analysis
SEA can simulate the occurrence of events and their automatic analysis. The events are translated and analyzed as if they occurred on the local system and events and problem reports from analysis appear as automatic events do. Using the simulation, you can perform and end-to-end test of SEA.
The wsea tes[t] no longer accepts the "inp[ut]" argument. Hence the following command that existed in WEBES versions prior to 4.5 has been replaced with a new command.
wsea tes[t] inp[ut]This command is now replaced with wsea ana inp[ut] command. See section 5.6.2 Manual Analysis for the new syntax. Use the following command to test SEA, from event detection to analysis and notification:
wsea testThis command sends an event with header fields but no further content to the system's error logging API. The action taken with this event is dependent on the system:
If the command was run on a supported platform, the system's error logging service takes the event content and wraps it with a Common Event Header (CEH). This is necessary because SEA only recognizes events with a CEH or a Storage Event Header (SEH). After the CEH is created and all its fields are populated, the event is written to the error log where it can be processed by automatic analysis, generate a problem report, and trigger notification.
The event generated by the test command will be logged with a CEH on the following operating systems and platforms:
OpenVMS 7.1–2 and 7.2 and above on all platforms
The error logging service on Windows does not wrap event content with a CEH since that is usually done by the device drivers themselves. So, like a device driver, the test command creates a mock CEH which is used as the event content and passed to the system error logging API. The command does not provide values for all the fields in the mock CEH. Only the fields critical to translation, analysis, and human identification (including time, computer name, OS type and event ID) are given valid values. Most other fields are set to 0 or NULL values and do not affect translation or analysis. After Windows receives the event, it adds a Windows NT header and the event is appended to the system error log. Once in the error log the event is processed by automatic analysis, generates a problem report, and triggers notification.