Evaluation Summary

An Evaluation Summary is created each time you evaluate a domain, and is persisted in the Guardian Workspace. The Evaluation Summary editor in the Document Pane enables you to interact with the Evaluation Summary and determine if you need to take any corrective action.

Conduct an evaluation. An Evaluation Summary is opened automatically when the evaluation completes.
Double-click an Evaluation Summary entry in the Evaluation History folder of the Domain Explorer.

Evaluation Summary Tabs

On the bottom of the Evaluation Summary editor are the following tabs for the different Evaluation Summary representations. Please note that these representations are read only:

Overview - provides evaluation statistics and a list of detected signatures. It also includes a description and remedy recommendation for each signature detected in the evaluation. It contains the following sections. Each section can be expanded or collapsed by clicking the triangle icon in the heading.

General Information - the target domain name, the signature bundle evaluated, the date and time of the evaluation, the length of time to conduct the evaluation, and the number of signatures targeted, detected, not detected, and undetectable in the evaluation.

For a given bundle of signatures, some signatures may not be used in the evaluation because they target different products than the domain has. The ones that do target what the domain has are counted as Targeted Signatures. The Targeted Signatures are divided into Detected Signatures, which are actually found on the domain; and Undetected Signatures, which are not found on the domain. If a signature fails to evaluate, it is counted as an Undetectable Signature, and is considered flawed.

Detected Signatures - a table that includes information about every signature detected in the evaluation, including the signature name, identification number, severity, area of impact, and BEA product affected. It also includes the signature topic and subtopic, which further narrow the category of potential problem found. If you submitted any support cases to BEA, the case information is listed as well.

Clicking a detected signature displays information about it in the Description and Remedy sections. Information about the first detected signature is displayed by default. You can sort the detected signature table by clicking any of the column headings. The detected signatures are sorted by severity and name by default.

The Severity column of the detected signature table includes an icon that approximates the amount of attention you should give each signature that has been detected.

Icon	Severity
	Critical
	Warning
	Informational

Description - information about the signature, from the signature XML file itself. Description includes the signature name, severity, category of impact (for example, Server Outage, Performance, or User Viewable Error), and a detailed description.
Remedy - an explanation of how to resolve the potential problem, from the signature XML file itself. It includes the servers impacted by the signature and links to get more information about the potential problem.

Remedy also includes a link, Get more help from BEA Support, which opens the Support Case Wizard. Opening a support case enables you to get more help from BEA to analyze and repair the potential problem that the signature detected.

Source - provides the actual XML source from the Evaluation Summary. It includes the raw data for each detected and undetected signature, and can be copied to your paste buffer or printed with the context menu. You can access the context menu by right-clicking inside the Evaluation Summary.
Report - provides all the information contained in the Overview tab in a printer friendly format. It can also be copied into your paste buffer or printed with the context menu.

Evaluation Summary Outline View

When the Outline View is open and the Evaluation Summary editor is active, you can use the Outline View to control what the Evaluation Summary editor displays. Clicking the Overview, Source, and Report nodes in the Outline View brings the corresponding tab of the Evaluation Summary editor to the forefront. Expanding the Outline View Source node enables you to select specific XML tag names, causing the Evaluation Summary editor to jump to those tags and highlight them.