You are on page 1of 8

Search and Classification Engine (TREX)

Purpose
Search and Classification (TREX) is the central SAP NetWeaver search engine that provides underlying search technology and functions for Enterprise Knowledge Management and Search Engine Service (SES). TREX offers an integrated set of services and is a basic part of the SAP NetWeaver Search Integration Capabilities. TREX services include search and retrieval in large document collections, text mining, automatic document classification, and search and aggregation of structured data in SAP applications. TREX can handle text from documents in numerous formats, including Microsoft Office and Adobe formats (PDF), and more than 30 languages. TREX search options, such as exact, Boolean, fuzzy, or linguistic searches, and classification options such as query-based or example-based classification, offer great power and flexibility to end users. The TREX APIs are not open for customer development. But TREX functions and services can be accessed through the APIs of SAP applications that provide configurable access to TREX services (for example Search Engine Service (SES) and Enterprise Knowledge Management (EKM)).

TREX Architecture
The following graphic depicts the different components of TREX:

TREX Components
TREX comprises the following central components:

Java client and ABAP client TREX provides programming interfaces (Application Programming Interfaces, APIs) for the languages Java and ABAP, which allow access to all TREX functions. The Java interface (Java client) is part of the Application Server (AS) Java as a TREX service. The ABAP interface (ABAP client) is part of the Application Server (AS) ABAP. These APIs are released for SAP-internal development only. 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 document, 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, 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, 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 is always active but becomes especially important in distributed multi-host TREX landscapes. The name server has the following tasks: Managing topology data, coordinating replication services, balancing the load, and ensuring high availability.

For TREX details, see the engine documentation for

Search and Classification (TREX).

Search Engine Service (SES)


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 (AS) ABAP. SES accesses the TREX functions through the TREX ABAP client. SES replicates the business objects from the ABAP application to TREX, so that it can apply TREX indexing and search functions to them. When a user enters a search query, the TREX system responds to it, not the database for the ABAP application.

TREX Scalability and Distribution


Search and Classification (TREX) offers a flexible architecture and can be adapted to different requirements. You can scale TREX if necessary. Your options range from a minimal system with one host, to a large distributed server landscape. Single-Host System A minimal TREX system consists of a single host that provides all TREX functions (indexing, classification, and searching). You can use a minimal system as a demo and test system, or as a

production system. For a production system, SAP recommends that you install TREX on a dedicated host that is used exclusively for TREX.

Multiple-Host System You have numerous options for scaling TREX. You use a scaled scenario to distribute the search and indexing load among several hosts and to ensure the availability of TREX. In a multiple-host system, the individual hosts are responsible for different tasks depending on which TREX components run on them. For example, you can set up dedicated search servers with copies of the original indexes and configure automatic index replication to keep the copies up-to-date. Example The graphic below shows an example for a distributed TREX system:

Explanation of abbreviations: Master Server: M NS = Master Name Server; M QS = Master Queue Server; M IS = Master Index Server Slave-Server: S NS = Slave Name Server; S IS = Slave Index Server; Backup-Server: B NS = Backup Name Server; B QS = Backup Queue Server; B IS = Backup Index Server Other Servers: RFC = RFC Server; WS = Web Server; PP = Preprocessor Data: Q = Queue; MI = Master Index; SI = Slave Index; SN = Index Snapshot; T = Topology File

For details on TREX distribution options and implementation, see the Configuration Guide Distributed Search and Classification (TREX) Systems on SAP Service Marketplaceservice.sap.com/instguidesNW70

Search Integration Capabilities


Purpose
Enterprise Knowledge Management, Search Engine Service (SES), and Search and Classification (TREX) provide a framework for enterprise-wide search technology to search structured data (business objects) and unstructured data (documents). For more information, see: Document Search with Enterprise Knowledge Management Enterprise Knowledge Management provides a document repository framework that allows users to search across documents (unstructured data) using the search engine technology of Search and Classification (TREX). Business Object Search with Search Engine Service (SES) Search Engine Service (SES) provides a search and indexing framework that allows users to search for business objects (structured data) using the search engine technology of Search and Classification (TREX). Search and Classification Engine (TREX) Search and Classification (TREX) is the central SAP NetWeaver search engine that offers underlying search technology and functions for Enterprise Knowledge Management and Search Engine Service (SES). The following graphic illustrates how KM, SES, and TREX are integrated in a single framework:

SAP Applications Using SAP Search Integration Capabilities


Structured Data: Searching For Business Objects
To search across structured data (business objects), SAP applications have two options for using the search capabilities of Search and Classification (TREX) and Search Engine Service (SES): SAP applications using TREX directly to search structured data SAP applications using SES to search structured data PLM (Product Lifecycle Management) BW (Business Information Warehouse) CRM (Customer Relationship Management)

SAP Applications Using TREX Directly to Search Structured Data

CRM ISA (Internet Sales) CRM SAF/CIC (Software Agent Framework, Customer Information Center) CRM e-Selling,

HR-HCM (Human Resources/Human Capital Management) e-Recruiting, e-Learning, and Expert Finder SRM (Supply Relationship Management) Asset Accounting Automotive DBM Controlling

SAP Application Using SES to Search Structured Data

Enterprise Asset Management Financial Accounting Industry Accounting IPPE Learning Solution Master Data Management PLM Master Data Management Public Sector Accounting Quality Management Real Estate

Unstructured Data: Searching For Documents


To search unstructured data (documents), SAP applications use the capabilities of the following components: Enterprise Knowledge Management (Repository Framework)

TREX 7.0 for SAP NetWeaver 7.0


Purpose
Applications based on SAP NetWeaver 7.0 use TREX 7.0. These applications can optionally use TREX 7.1 because each version of the TREX ABAP client and the TREX Java client is compatible with TREX 7.1.

More information: TREX 7.1 for SAP NetWeaver 7.0

Integration
Search Engine Service (SES) The Search Engine Service (SES) enables users to search for business objects. SES is part of the SAP NetWeaver Application Server and access TREX functions through the TREX ABAP client (for details, see Administration of the Search Engine Service). Search Integration Capabilities TREX is part of the SAP Search Integration capabilities. Search and Classification (TREX), Knowledge Management (KM), and Search Engine Service (SES) together make up the integrated SAP search technology for company-wide searches in unstructured and structured data (document collections and business objects).

Documentation Structure
This documentation is organized into the following areas: TREX Architecture This area contains information about the TREX architecture, the TREX components, and their functions. TREX Configuration This area contains all relevant procedures that describe how you can configure TREX. The configuration is organized as follows:

Post-Installation Configuration Initial Configuration

Advanced Configuration

TREX Administration Here you can find information about administrating TREX:

Starting and Stopping TREX TREX Admin Tools Data Backup and Restore for TREX Monitoring TREX with CCMS Administration of the Search Engine Service

TREX Architecture TREX is based on a client/server architecture. The client component is integrated into the application that uses the TREX functions, and allows communication with the TREX servers. The server component processes the requests; it indexes and classifies documents and answers search queries. The client component is subdivided into the Java client and ABAP client. The server component is subdivided into the following servers:

Web server with TREX extension RFC server Queue server Preprocessor Index server Name server

The graphic below shows the individual components and the communication between components:

Through below link you will get TREX application TOTAL Architect http://help.sap.com/saphelp_nw2004s/helpdata/en/40/83505303bd5616e10000000 a114cbd/frameset.htm

You might also like