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
General considerations for importing documents
The following are general considerations for importing documents into Service Manager:
- If the Service Manager license does not include SOAP API license, the sm.ini file needs to include the following parameter: allowwsdlretrieval:1.
- Set refresh interval in the Knowledge_Library to -1 to turn off incremental updates during a large import.
- We recommend using a <Legacyid> element. The value of this element should be unique across ALL documents. If <Legacyid> is specified, the import queries the kmdocument table for the legacyid. If an existing record in kmdocument contains a legacyid matching the value in the <Legacyid> element of the source xml, the kmdocument record is updated with the information in the source xml. If no existing record in kmdocument is found with a legacyid matching the value in the <Legacyid> element, the xml source is inserted as a new kmdocument.
- Elements in the source xml files must have corresponding fields in the kmdocument table in Service Manager (the kmdocument record in the dbdict table), and they must be included in the Web services API.
- Fields that are in a document xml file that are not in the dbdict are omitted on import, but the documents are imported.
- Elements with data containing HTML markup or any special characters that are illegal in XML should be CDATA wrapped to prevent the XML parser from throwing an exception.
Related topics
