TREX provides SAP applications inside and outside of SAP NetWeaver with intelligent search, classification, and aggregation functions. During the installation of SAP NetWeaver, you can install TREX as a stand-alone engine, to make its functions available as part of an SAP NetWeaver scenario for the application in question.
Search and Classification (TREX) and Knowledge Management (KM) together provide integrated SAP search technology for company-wide searches in structured and unstructured data (document collections and business objects).
The graphic below shows the individual components and how they communicate.
TREX comprises the following central components:
● Java client and ABAP client
TREX provides programming interfaces (Application Programming Interfaces, APIs) for the Java and ABAP languages. These interfaces are also called the Java client and the ABAP client. The interfaces allow access to all TREX functions. You can use the interfaces to create indexes and queues, to perform indexing, and to perform searches. The interfaces are part of the NetWeaver Application Server (NW AS).
● Web server with TREX extension
The Web server is responsible for the communication between Java applications and the TREX servers. A TREX component that enhances the Web server with TREX-specific functions is installed on the Web server.
● RFC server
The RFC server is responsible for the communication between an SAP system and the TREX servers. The SAP system sends requests to an RFC server using an SAP Gateway. The RFC server converts the requests to a TREX-internal format and then forwards them to the responsible TREX servers.
● Queue server
The queue server coordinates the processing steps that take place during indexing. It collects incoming documents and triggers preprocessing by the preprocessor and further processing by the index server.
● Preprocessor
The preprocessor preprocesses documents and search queries. Document preprocessing comprises several steps: Loading documents, filtering documents, and analyzing documents linguistically. During search queries, the preprocessor performs a linguistic analysis.
● Index Server
The index server indexes and classifies documents and answers search queries. The processing takes place in the engines that belong to the index server: Search engine, text-mining engine, and attribute engine.
● Name Server
The name server manages information on the entire TREX system. It makes sure that the TREX servers can communicate with each other and that they receive all necessary information. It has the following tasks: Managing topology data, coordinating replication services, balancing the load, and ensuring high availability.
The Search Engine Service (SES) enables users to search for business objects. SES is not a TREX component; it is part of the SAP NetWeaver Application Server. SES accesses the TREX functions through the TREX ABAP client.
The table below tells you where you can find further information on the technical system landscape.
Topic |
Guide/Tool |
Quick Link on the SAP Service Marketplace (service.sap.com) |
TREX components |
|
|
Technical configuration |
● SAP NetWeaver 2004s Search and Classification (TREX) Single Host installation guide ● SAP NetWeaver 2004s Search and Classification (TREX) Multiple Hosts installation guide |
For more
information, see the SAP Service Marketplace at
service.sap.com/ |
Security |
|