The TREX advanced configuration comprises the following areas:
TREX is based on a flexible architecture that allows distributed installation and thus modification to suit various different requirements. There are numerous ways of scaling TREX. You can distribute TREX components among several hosts and install individual components more than once. You can use a scaled scenario to distribute the search and indexing load among several hosts and to ensure the availability of TREX.
You can configure secure communication between TREX and the application using it (for example, SAP Enterprise Portal or SAP Customer Relationship Management).
You can use the monitoring functions of CCMS (Computing Center Management System) to monitor Search and Classification (TREX). This documentation describes how to configure the monitoring functions.
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.
This configuration comprises procedures that allow you to check problems that occur and solve them, if necessary. You can also improve TREX performance. In contrast to the configuration steps following installation, these configuration steps are not necessary in order for TREX to work correctly in the default configuration as a single-host system and to allow use by an application.
You want to change the host names of the servers on which TREX is installed. You can do this for the following scenarios:
Installing TREX with Virtual Host Names
Changing the TREX Host Name (Single Host)
Changing TREX Host Names (Multiple Hosts)