The TREX Java client (part of the J2EE Engine) accesses the TREX functions using the TREX Web server. Communication between the TREX Java client and the TREX Web server takes place using HTTP or HTTPS and XML. The TREX name server offers a watchdog function for monitoring active TREX servers. The watchdog regulularly checks whether the active TREX servers (in this case, the TREX Web server) can still be reached. The name server is then able to recognize the Web server and forward its address on request. If the TREX Java client and TREX Web server are to communicate using HTTPS protocol, you have to configure the TREX name server for secure communication with the TREX Web server.
You have installed and configured the SAP cryptography tool SAPGENPSE on the host on which the TREX preprocessor is running. SAPGENPSE 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 on SAP Service Marketplace. For more information aboutdownloading and configuring SAPGENPSE, see Using Cryptography Tools.
You configure the TREX name server for secure communication with the TREX Web server (IIS/Windows or Apahe/UNIX) using HTTPS by carrying out the following steps:
Configure the TREXWebServer.ini INI file
Import the client and root certificates
Authenticate the TREX name server
Enter the owner and issuer of the client certificate in the TREXcert.ini file (IIS/Windows)
Enter the owner and issuer of the client certificate in httpd.conf (Apache/UNIX)
The graphic below gives an overview of the process flow.