Testing a component signature

Before you run the Discovery Job, you can test whether servers satisfy the signature conditions that you specified on the Discover tab of the component template.

This procedure does not actually associate a component with any servers. To perform that procedure, see Creating-and-modifying-Component-Discovery-Jobs or Adding-components-to-servers-manually.

To test a component signature

1. On the Discover tab of the component template, click the Edit icon on the right.
2. In the Rule Editor, click Test the Rule .
   The Test Signature window opens.
3. In the Target Selection area on the left, click Add Servers .
   The Add Servers window opens.
4. Select one or more servers on which you want to test the component template signature, and click the right arrow to move your selections to the right panel.
5. Click OK to close the Add Servers window.  The selected servers appear in the Target Selection area. To view the list, you might need to expand the Servers tree.
    To remove a server, select it and click Remove Item .

6. Click Run Test to test the signature on all selected servers.
    The test runs. Discovered components appear under the servers, each with a green success or red failure icon beside it.

   Note

   To stop the test run before it completes running, click Stop Test .

7. For more details about the success or failure of component discovery on a specific server, select the discovered component.
    Two panes display on the right. The top pane displays the full signature as defined through the Rule Editor, including all its conditions and if-then conditional constructs. Any condition within the rule that caused the rule to end in Non-compliant status appears in red. The overall compliance status for the full signature appears at the top, as well as an indication of whether any exceptions were defined. The bottom pane displays compliance details on the target component for a selected condition.

8. In the top pane, select a condition within the signature.
    In the bottom pane, the condition is parsed into columns for the left-hand-side (LHS) operand, comparison operator, and right-hand-side (RHS) operand. An additional Success column indicates whether the component satisfied the condition (either for true or for false). The actual value detected on the target component appears in brackets after the LHS operand so that you can see how it compares to the value in the RHS operand.

   Note

   In the top pane, condition operands that are very long are truncated and end with an ellipsis (...).
    Cardinality conditions are not parsed in the bottom pane. A basic condition is not parsed if it contains wild cards and was satisfied by the component.
    If a basic condition is preceded by a NOT logical operator, the Success column in the bottom pane shows a value of true when the condition appears in red in the top pane.
    Lines that were not analyzed appear in gray in the rule in the top pane. For example: if, then, or else blocks in a conditional construct that were skipped or not reached.
    In a conditional construct only one then line, or the last else line, may appear in red. All if and elseif lines always appear in black font.

9. If a condition includes ACL information, you can view detailed ACL information for a target server by doing the following:
   1. Select an entry in the Target pane that includes ACL information and click View ACL Details .
       A details window opens. It provides a list of applicable permissions.
   2. Select a name in the Access Control List, and then click View ACL Details .
       Another detail window shows permissions granted to the name you selected.
   3. Click Close and then click Close again to close both detail windows.
10. Click Close to close the Test Signature window.