The TREX preprocessor is responsible for preparing documents to be indexed by the TREX engines. The Web server of the application using TREX (for example, SAP Enterprise Portal) transfers documents to be indexed to the preprocessor in the form of a URI that references the storage location of the document. The preprocessor resolves the URIs, is redirected to this URI, and uses HTTP to fetch the actual document from the repository in question. If this communication takes place using HTTPS, you have to configure anonymous client authentication between the preprocessor and the Web server of the application using TREX. You do this by importing the root certificate of the Web server to a keystore on the preprocessor.
If the actual storage location for the documents that the preprocessor refers to is located on a Web server outside of a secure system landscape, you must also register the root certificate of this Web server with the preprocessor by importing it on the server in question.
Use the cryptography tool SAPGENPSE to configure the preprocessor for HTTPs. This is a part of the SAP Cryptographic Library, which is the standard security product delivered by SAP for encryption functions in SAP systems. The SAP Cryptographic Library is available for download by authorized customers in the SAP Service Marketplace.
To configure anonymous client authentication between the preprocessor and the Web server of the application using TREX, you need to
You carry out the following steps to do this:
The graphic below gives an overview of administrative tasks.
You have configured anonymous client authentication between the TREX preprocessor and the Web server of the application using TREX.