Configuring the Java Client for Secure TREXNet 

Purpose

The TREX Java client communicates directly with the TREX name server using TREXNet. The Java client asks the name server for the address of the currently active TREX Web server so that it can send requests to the relevant Web server using HTTP/HTTPS. You configure a secure TREXNet connection so that the Java client and name server can communicate securely with each other.

The configuration of secure communication using TREXNet between the TREX Java client and the TREX name server is only beneficial if you also make the connection between the other TREX servers secure using TREXNet.

Prerequisites

You configure the TREX Java client for secure communication with the TREX name server using TREXNet in the SAP NetWeaver Administrator.

Procedure

...

       1.      Start the SAP NetWeaver Administrator in the Application Server Java.

       2.      Navigate to Configuration Management ® Infrastructure Management ® Java System Properties.

The Java System Properties: Overview window appears.

       3.      In the Details area, choose Services.

       4.      In Services, find the TREX service by entering trex as the search term in the filter area.

The entry trex.service appears. In the Extended Details area, the Properties tab page contains the properties for the TREX service (TREX Java client).

       5.      Enter the values displayed in the table below for the parameters.

TREX Service (TREX Java Client) Parameters for Secure Communication

Parameter	Input Value
communication.issecure	true
default.keystore	TREXKeyStore
default.truststore	TrustedCAs

       6.      Choose Update after every entry you make to ensure that the system adopts the changed values.

       7.      Choose Save Properties from the upper menu bar (disk symbol for saving) to save your entries.

       8.      Restart the TREXServices so that your changes are accepted.

Result

You have configured the TREX Java client for secure communication with the TREX name server using TREXNet.

You now configure the sapprofile.ini INI file so that the Java client can communicate with the name server and so that all other TREX servers (name server, Web server, preprocessor, index server, and queue server) can also communicate with one another using TREXNet and a secure connection.