The TREX preprocessor is responsible for preparing documents to be indexed by the TREX engines. The application using TREX (for example, Content Management in SAP Enterprise Portal) transfers documents to be indexed to the preprocessor in the form of URIs that reference the storage location of the documents. The preprocessor resolves these URIs and then collects the actual documents using a Web server and HTTP.
Access to Web pages can take place using a Proxy server regardless of whether the pages are in the Internet or in an Intranet. If you want to index documents that can only be accessed using a proxy server, you have to register the proxy server with the TREX preprocessor.
There might also be documents in your environment that can be accessed without a proxy server, for example, documents on local servers or your enterprise's external homepage. You can inform the preprocessor of the servers it can access without a proxy server. This speeds up the processing of documents on these servers.
You specified settings for the proxy server when you installed TREX. If you want to change this later on, modify the TREXPreprocessor.ini configuration file on the server on which the TREX preprocessor is running.
The graphic below shows a portal scenario. Some of the documents to be indexed are located on servers on the intranet, others on servers on the Internet. The documents on the Internet can only be reached using a proxy server. The proxy server is not needed for documents on the intranet.
Entert he proxy server into the section [httpclient] in the configuration file TREXPreprocessor.ini so that TREX can load external documents. Enter exclusion rules for internal documents into the section [proxyrules].