Show TOC

Configuring the Java Client for Secure TREXNetLocate this document in the navigation structure


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.


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

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

  2. Navigate to Start of the navigation path Configuration Management Next navigation step Infrastructure Next navigation step Java System Properties End of the navigation path.

    The Java System Properties: Overview appears.

  3. In the Details area, choose the Services tab page.

  4. Search for the TREX service in Services by entering the name trex as a search term in the filter area.

    The entry trex.service appears. In the Extended Details area, under the Properties tab, you can see the properties of the TREX service (TREX Java client).

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


Input Value







  1. Choose Update after every input to make sure that the changed values are accepted.

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

  3. Stop and start TREXServices to make sure that the changes are accepted.


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.