Escolar Documentos
Profissional Documentos
Cultura Documentos
Service Desk
Full-Text Search in Support Messages
Fuzzy Search
Fuzzy or error-tolerant search is a more sophisticated TREX search engine function
Fuzzy search provides more flexibility than exact search by finding approximate matches for the search terms
These matches have similar spelling to the search terms: they can be transformed to the search terms by a pre-specified
number of single-character changes
You can set this “editing distance” measure of similarity to tolerate more or less error or fuzziness
Fuzzy or error-tolerant search is especially useful if you are not sure of the exact spelling of a word, if you make a spelling
mistake when entering a search term, or if a spelling mistake has been made in the document that you are looking for
Examples: A search for <presidant> (typing error) also finds documents that contain the correct spelling “president”. A search
for <Meier> also finds “Meyer” and “Maier”.
Fuzzy search is used to implement a “Did you mean …” feature that suggests an alternative search term if the entered term
looks like a misspelling of a similar term
Linguistic Search
Linguistic search finds matches that are related to the search term only via some linguistic transformation, such as singular to
plural for nouns or past to present tense for verbs
The search algorithm reduces the search term to a word stem, then searches for all variants with this stem
Example: A search for <mice> also finds “mouse”. A search for either <mouse> or <catch> can find a document containing the
sentence “The traps caught the mice”.
Configure the full-text search and the knowledge database for Service Desk in SAP Solution Manager
Configure the Software Agent Framework (SAF) and set-up the search machine and knowledge database
Compile the initial index for messages (CRM_OBJECT) and/or problems and solutions created (SDB)
Activate action for delta compilation (only for CRM_OBJECT messages) and schedule delta compilation background
job
1. Set up Remote Connection between TREX Search Engine and SAP Solution Manager
1. Open the SAP Solution Manager Implementation Guide (IMG) using transaction SPRO
2. Call SAP Solution Manager -> Cross-Scenario Settings -> TREX Setup
3. Follow the instructions within the IMG activity documentation, which explains how you can maintain the
RFC connection of type T (TCP/IP) in the Solution Manager
Hardware
Depending on the application scenario, when running under Windows, TREX requires approximately the following hardware:
Small: PC with P4 class CPU (with clock speed at least 1 GHz), 1 GB RAM, and 20 GB hard drive. If TREX shares a
server, it needs at least 1 CPU, 1 GB RAM, and 20 GB storage for itself.
Medium: Server with 2 P4 class CPUs, at least 4 GB RAM, and 40 GB storage. These requirements are doubled if
TREX runs together with SAP Enterprise Portal, SAP R/3, or SAP CRM.
Large: Servers with a total of at least 4 P4 class CPUs, 8 GB RAM, and 120 GB storage. For very large applications,
TREX can use 24 or more blade servers.
Hardware requirements for other operating systems are similar
TREX 7.0 or 7.1 has been developed to run smoothly on blade server hardware