The configuration of Search and Classification (TREX) is organized as follows:
You must work through these steps immediately after the installation, so that a single-host installation of TREX works correctly and can be addressed using an ABAP or Java application. The documentation distinguishes between configuration steps that you have to complete on the TREX server side and configuration steps that you have to complete on the client side, that is, on the side of the application using TREX.
The initial configuration comprises procedures that allow you to check problems that occur and solve them, if necessary. You can also improve TREX performance. These configuration steps are not required in order for TREX to work correctly in the default configuration and allow use by an application.
The advanced configuration comprises the following areas:
TREX supports the indexing of documents that exist in different languages. When TREX is installed, you select the languages to be identified by language recognition. You can retrospectively configure TREX to recognize additional languages.
Documents whose content and attributes can be indexed and searched by TREX can exist in numerous different file formats. You can configure which file formats you want to exclude from processing and which parts of XML and HTML files you want to exclude from indexing.
The TREX preprocessor can access documents on Web pages using a proxy server. You can configure the settings for the proxy server.
Some TREX functions are implemented as Python extensions. If the application from which TREX is used uses these functions, you have to activate the Python extensions.
The TREX Java client is implemented as a TREX service in the J2EE engine. You can use the SAP NetWeaver Administrator to configure TREX caches and the TREX Java client.
TREX provides the option of activating delta indexes. This allows you to update indexes faster and improve the performance of TREX.
You can change the name of the host on which you installed TREX later on, or you can install TREX with a virtual host name. You can do this for both single-host and multiple host installations.
You can configure secure communication between TREX and the application using it (for example, SAP Enterprise Portal or SAP Customer Relationship Management).