Show TOC

Changing Proxy Server SettingsLocate this document in the navigation structure


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].


  1. Open the <TREX_Installation_Directory>\TrexPreprocessor.ini configuration file on the server on which the TREX preprocessor is running. Use a text editor to do this.
  2. Modify the following parameters in the [httpclient] and [proxyrules] section:


    proxyhost=<name_of_proxy> (host name and domain of the proxy server)


    proxyport=<proxy_port> (port of the proxy server)



    proxyuser=<user_for_the_proxy> (optional)

    You only need to enhance the line proxyuser if a user ID is needed to access the proxy server.

    proxypassword=<passowrd_for_user> (optional)

    You only need to enhance the line ' proxypassword=' if a password is also needed for the user ID.


    You can specify the password for the proxy user during the TREX installation. You can use a script to change this password later on or to define a password if you did not enter one when installing TREX. For more information, see Configuration of the TREX Security Settings:

    Specifying a Password for the Proxy Server.


    The listing of the parameters cannot contain empty lines. Keep to the format outlined above. The system distinguishes between lowercase and uppercase.


    Specify the addresses for which the proxy server is not to be used. You normally enter one or more character strings in which the addresses in your intranet end.

    Example or


    Do not use the asterisk (*) as a placeholder. Lines that begin with # or ! are treated as comments and are therefore ignored. This is also true for IP addresses. To exclude the IP address space, add the line 10.10 to the [proxyrules] section. This ensures that no proxy is used for URLs that contain IP addresses in this space.

  3. Save the file and close the text editor.
  4. You have to stop and restart the TREX preprocessor so that it recognizes the changes made in the TREXPreprocessor.ini configuration file. In the TREX Admin Tool (Standalone), you use the following function to do this:

    Starting and Stopping the TREX Servers. Note that the TREX daemon automatically restarts the server after it has been stopped.