Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Configuration Validation Rules
The following provides instructions about using configuration validation rules in the Service Manager Doctor tool.
Configuration rule file
Caution It is not recommended that you edit the configuration rule file manually in this version of the tool.
The configuration rule file is an XML file with predefined rules that are used to validate Service Manager server configurations. All configuration information is based on the sm.ini and sm.cfg files, where sm.cfg is prioritized higher than sm.ini.
The elements of the configuration rule file include source, domain, rule, condition, conditonrule, operation, and output. Configuration rules for all configurations should be defined within the configuration source. Configuration rules used for specific validation should be defined within a specific domain. There can be multiple domains within each source, and multiple rules within each domain. See Appendix C. Rule Configuration File Snippets.
Considerations for updating the rule file
- This tool includes an
SM_Configuration_Rule.xsdfile to maintain the integrity of the rule file. Detailed messages are displayed in the validation results, including information about the row, column, and other violation specifics. - If one rule serves as a condition for another rule, the first rule cannot have conditions of its own. Or, a
TWO_LEVEL_CONDITION_FOUNDerror is returned. - For operation elements within a rule element, the "param" and "action" attributes are required. The "target" and "type" attributes are optional, but they are mutually dependent. If one parameter is defined, you must define the other one too.
- For condition elements, if "operator" and "target" are not defined, they default to
andandtruerespectively. - In addition to customized rules, you can use the generic rules directly: is32OS, is64OS, isUnix, and isWindows.
- An error 100018 is returned if the XML content cannot be parsed.
- In the current version of the tool, only the configuration data source is editable, which includes both the
sm.iniandsm.cfgfiles.
Validation results
Validation results are included as part of the command output for the conf -ini and conf -cfg commands in command-line mode. In GUI mode, a separate column is displayed next to the command results if a rule failure is detected.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-ITSM@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: