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 addresses of the currently active TREX Web server so that it can then 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 visual administrator of the J2EE Engine.

Procedure

       1.      Start the visual administrator in the J2EE Engine.

       2.      In the left-hand window of the visual administrator, choose the Cluster tab.

       3.      Expand the node of the server on which the J2EE Engine is running.

       4.      Expand the Services node.

       5.      Choose the entry TREX Service under Services.

The configuration parameters of the TREX Java client appear in the right-hand window beneath the Properties tab.

       6.      Enter the values displayed in the table for the relevant parameters.

TREX Java Client Parameters for Secure Communication

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

 

       7.      Choose Update after every entry so that the J2EE Engine accepts the changed values.

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

       9.      Stop and restart the TREX services 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 ini file sapprofile.ini so that the Java client can communicate with teh 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.