Show TOC

Configuring the HTTP ConnectionLocate this document in the navigation structure


If you want to connect the TREX system to a Java application, you must register at least one name server with the TREX Java client.


We recommend that you specify all master name servers on the client side. This increases the availability of the connection between the application and TREX. If the Java client cannot reach one master name server, it can attempt to reach another instead.

The client-side configuration is separate from the server-side configuration. In principle, you can enter any name servers on the client side, regardless of their server-side role.


  1. If you do not know the addresses of the master name servers, look for them in the TREX admin tool at Landscape → Configuration: <host>:<name_server_port><:name server mode>.
  2. Change the Java client parameters for all server processes in the cluster as follows:
    1. Enter one master name server in the following parameter:

      nameserver.address tcpip://<one_address>

    2. Specify the TREX backup name servers in the nameserver.backupserverlist parameter. When doing so, separate the backup name servers using a comma and use the following format: tcpip://<host1>:<port1>,tcpip://<host2>:<port2>, …

      The addresses of the master name servers must be configured for all server processes in the cluster. Otherwise the connection between the J2EE Engine and TREX cannot be established.