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 |
|
- Knowledge Management migration
- Import documents into Service Manager
- XML file specification for Knowledge Management migration
- Sample import record migration file
- General considerations for importing documents into Service Manager
- XML source document considerations for importing
- Document import considerations for attachments
- Configure the wsdl2java.bat file
- Configure the wsdl2java.sh file
- Running the wsdl2java command file
- Configure the runDocumentImport.bat file
- Configure the runDocumentImport.sh file
- Running the runDocumentImport command file
- Reconciling unresolved links
- Using the knowledgecreator.log file
- KMSCCoreImport utility
- KMDocumentExport utility
Using the knowledgecreator.log file
After running document import (either runDocumentImport.bat or runDocumentImport.sh), examine the knowledgecreator.log file. Correct any file errors noted, and then re-run the import, if desired.
The end of the file contains the following import statistics:
-Imported Documents...................: 4008
-Skipped Documents.....................: 12
-Reject Documents.......................: 4
-Imported Attachments.................: 1
-Skipped Attachments...................: 4
Skipped files include any non-xml files that are left in the import folder. For example, an error such as "org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup." indicates that the XML probably contains special characters that could not be parsed.
You can edit and correct the files that were skipped and re-run the import.
If the meta data for any imported file contains a field that was not defined in the kmdocument data dictionary (dbdict), then this field's value was not imported. The log file lists any undefined fields. You can add the field to the kmdocument dbdict and re-run the import to populate the field's value.
Related topics
Knowledge Management migration
Running the runDocumentImport command file
