TREX Basic Configuration

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_nwes72/helpdata/en/45/475bbc1ca14d35e10000000a114a6b/content.htm
Created on August 19, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 13

Table of content
1 TREX Basic Configuration
1.1 Wizard-Based Basic Configuration for TREX
1.2 TREX Post-Installation Configuration
1.2.1 Starting the TREX Admin Tool
1.2.2 Configuring the TREX Web Server
1.2.3 Configuring TREX Proxy Settings
1.2.4 Checking Proxy Settings
1.2.5 Selecting Languages for TREX Language Recognition
1.2.6 Configuring TREX for the System Landscape Directory (SLD)
1.2.7 Checking Performance Settings for the Operating System
1.3 Connecting TREX with an Application
1.3.1 Connecting TREX with an ABAP Application (RFC Connection)
1.3.1.1 Creating a SAP System User for the TREX Admin Tool (Stand-Alone)
1.3.1.2 Determining the SAP System Connection Information
1.3.1.3 Configuring the RFC Connection in the TREX Admin Tool
1.3.2 Connecting TREX with a Java Application (HTTP Connection)
1.3.2.1 Specifying the Address of the TREX Name Server

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 13

1 TREX Basic Configuration

The TREX basic configuration comprises the following areas:
Wizard-Based Basic Configuration for TREX
The configuration wizard enables the automatic configuration of the settings that are required if the application using TREX communicates with TREX
using an HTTP or RFC connection.
TREX Post-Installation Configuration
After installing TREX, you carry out various technical configuration steps that are required so that TREX runs correctly with the standard configuration on
a single-host system and so that it can be used by an SAP application.
Connecting TREX with an Application
TREX can communicate with the application using it by means of an HTTP connection or an RFC connection. There are therefore two procedures for
connecting TREX with the application using it:
Connecting TREX with a Java Application (HTTP Connection)
Connecting TREX with an ABAP Application (RFC Connection)

Wizard-Based Basic Configuration for TREX

Use
The configuration wizard enables the automatic configuration of the settings that are required so that the application using TREX can communicate with TREX
using an HTTP connection.

Only execute template-based configuration if you have not configured TREX previously.

The wizard-based configuration of the settings that are required to enable the application using TREX to communicate with TREX using an
RFC connection is not currently supported. You therefore carry out the configuration steps required for this manually (more information:
Connecting TREX with an ABAP Application (RFC Connection)).

Procedure
1. Call the wizard-based configuration tool as described in Configuration Wizard.
2. Once you have selected the functional units that you want to configure using the configuration wizard, the Usage Type Overview Selection of
Configuration Flavors screen appears. Select Connect TREX in Further configuration tasks.
3. After completing additional configuration steps, you reach the Specifying the Address of the TREX Name Server page. Enter the address of one or
more TREX name servers. A TREX name server controls and monitors the HTTP connection between TREX and the application using TREX.

Result
You have used the configuration wizard to configure the HTTP connection between TREX and the application using it. You can also carry out the configuration
steps of the wizard-based configuration manually.
For information on this, see the following documentation:
Connecting TREX with an Application
Connecting TREX with an ABAP Application (RFC Connection)
Connecting TREX with a Java Application (HTTP Connection)

You carry out these steps manually if you have already carried out the wizard-based basic configuration previously and now want to configure
settings at a later time.

TREX Post-Installation Configuration

Purpose
After installing TREX, you carry out various technical configuration steps that are required so that TREX runs correctly with the standard configuration on a
single-host system and so that it can be used by an SAP application.

1.2.1 Starting the TREX Admin Tool

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 13

Prerequisites
On UNIX: Since the TREX admin tool has a graphical interface, you need an X server. You cannot use a terminal program that only supports text mode, such
as telnet.

Procedure
1. Log on with the user <sapsid>adm.
2. Carry out one of the following steps:
Operating system

Procedure

UNIX

Enter the following:

cd <TREX_DIR>
./TREXAdmin.sh

Windows

Start the TREX admin tool by double-clicking <TREX_DIR>\TREXAdmin.bat in

Windows Explorer.

1.2.2 Configuring the TREX Web Server

Use
Java applications that use TREX communicate with the TREX servers using HTTP/HTTPS by means of a Web server that has TREX-specific functions. After
installing TREX, you have to configure the TREX Web server so that your Java application can access TREX.

Prerequisites
You must have installed a Web server to use a TREX Web server for HTTP communication with the application using TREX:
UNIX: Apache Web Server
The TREX delivery includes an Apache Web server. The TREX installation process installs this server in the <TREX_DIR>/Apache directory.
Windows: Internet Information Server (IIS)
TREX only supports Windows IIS Version 6.0 or higher.
The TREX delivery does not contain the Internet Information Server (IIS), so you have to install an IIS 6.0 on your TREX host before configuring the
TREX Web server.

Make sure that the IIS is running correctly. To do so, activate the World Wide Web Publishing Service, IIS Admin Service, and HTTP SSL
in the Windows Services tool. Make sure that the Default Web Site runs on the IIS: To check whether this is the case, navigate to
Control Panel

Administrative Tools Computer Management

Services and Application

Internet

Information Services (IIS) Manager.

In a distributed TREX landscape, the password for the <sapsid>adm user must be identical on all hosts. This is also the case for the
SAPService<SAPSID> user.

Procedure
1. Start the TREX admin tool (stand-alone).
(See: Starting the TREX Admin Tool).
2. In the Landscape Connectivity window, go to the http tab page.
3. Choose Refresh.
4. Choose Add HttpServer .
The Set Admin User and Password window appears.

During the subsequent configuration steps, the system repeatedly asks you for the password for the <SAPSID>adm user and the SAP system
service user (SAPService<SAPSID>).These users and corresponding passwords were created during the TREX installation process.
Various error messages appear in the Configuration Status area of the window, telling you that the TREX Web server is not yet fully configured.
5. Choose Repair All .
The Set Admin User and Password window appears.
6. Choose Repair All again.
The Set SAPService <SAPSID> window appears.
The Set Admin User and Password window appears.
The Repair Results window appears and confirms that the system correctly created a TREX Web site and application pool.
The Set Admin User and Password window appears.
7. Choose Save to save your settings. Choose Reset to restore the previous settings.

Result
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 13

You have successfully configured the TREX Web server when the message No problems found appears in the Configuration Status area of the screen
and a green traffic light appears.

1.2.3 Configuring TREX Proxy Settings

Use
If there is a proxy server between the TREX servers and the documents to be indexed, specify the proxy server and define exclusion rules if necessary. This
configuration is important if you want to index the following items:
Documents on internal servers that can be accessed without a proxy server.
Web pages on external servers that can only be accessed using a proxy server.

Procedure
1. Start the TREX admin tool.
2. In the Preprocessor: Admin window, navigate to the Proxy Setting tab page.
Enter the proxy server in this area of the TREX admin tool. Since the proxy server should not be used for internal addresses, define exclusion rules for
internal addresses.
Proxy Server host name and domain of the proxy server
Example: proxy.mylocation.mycompany.com
Proxy Server Port port of the proxy server
Example: 8080
Proxy User user name needed to access the proxy server
Proxy User Password password defined for the user ID

For more information, see

Specifying a Password for the Proxy Server.
Proxy Exclusions exclusion rules. These rules define when the proxy server is not to be used. Separate multiple entries using a semicolon.

Examples of exclusion rules:

Do not use the proxy server to get URLs that end in mycompany.com:
mycompany.com
Do not use the proxy server to get IP addresses that start with 10: 10.

Do not use asterisks as placeholders.

3. Click Save to save your settings. Click Reset to restore the previous settings.

Result
You have configured the proxy server and the corresponding exclusion rules.

1.2.4 Checking Proxy Settings

Use
If an application is unable to communicate with TREX, it may be due to the application trying to access TREX using a proxy server. If this is the case, you
have to change the configuration so that access does not take place using the proxy server.
The procedure depends on the application concerned:
SAP Enterprise Portal 6.0 with Content Management
Other Java applications based on J2EE 6.40

Procedure
SAP Enterprise Portal 6.0 with Content Management
Check the settings in the portal at System Administration System Configuration Service Configuration Applications (Content Catalog)
com.sap.portal.ivs.httpservice Services proxy .
If a proxy server is entered there, you have to enter the TREX host in the field http Bypass Proxy Servers.
Other Java applications based on J2EE 6.40
For other Java applications, you have to check the configuration of the J2EE Engine. The proxy settings belong to the Java parameters. If a proxy server is
configured in the Java parameters, enter the TREX host in the parameter nonProxyHosts. You can choose one of the following options:
Alternative 1: D"http.nonProxyHosts=<hostname>.<mydomain>|localhost

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 13

For <hostname>.<domain>, enter the host name and domain (if necessary) of the TREX host.
Alternative 2: D"http.nonProxyHosts=*.<mydomain>|localhost
You can change the Java parameters using the SAP J2EE Engine GUI Config Tool. For more information about using this tool, see the SAP Library at the
Internet address help.sap.com Documentation SAP NetWeaver

Note that you have to specify the name of the TREX host in the same way both on TREX side in the TREX configuration files
(topology.ini, sapprofile.ini) and in the configuration of the J2EE Engine as described above. In case you specify the TREX host
name as fully qualified (e.g. PWDF12345.sap.corp) you have to do so on both sides. A mixed usage of host names does not work.

Selecting Languages for TREX Language Recognition

Use
TREX supports the indexing and analysis of documents in different languages. You can select languages to be identified by TREX language recognition.
The language of a document is needed so that the document in question can be placed in the correct language version of the index. For each language that
you select, TREX creates a separate language index. For example, if you select English, German, and French, TREX creates one English, one German, and
one French language index (see also:

Index Types).

Procedure
1. Start the TREX admin tool.
2. In the Preprocessor: Admin window, navigate to the Languages tab page.
The Languages for Document Analysis area contains an overview of languages that TREX supports. In this area, select the languages that you want
TREX to identify by means of document analysis.

Only select the languages that are relevant for your scenario. This optimizes performance during the language recognition process, and
therefore during the search and indexing process. The language recognition process gives better results if as few languages as possible are
used.
Languages for which TREX only provides restricted support are indicated by an asterisk (*).

For more information about these languages, see

Supported Languages with Restricted Functionality.

Configuring TREX for the System Landscape Directory (SLD)

Use
A modern computing environment consists of a number of hardware and software components that depend on each other with regard to installation, software
updates, and demands on interfaces. The SAP System Landscape Directory (SLD) simplifies the administration of your system landscape.
The SLD is a server application that communicates with a client application using the Hypertext Transfer Protocol (HTTP). The SLD server contains
component information, a landscape description, and a name reservation, which are based on the standard Common Information Model (CIM). The CIM
standard is a general schema for describing the elements in a system landscape. This standard is independent of any implementation.
The component description provides information about all available SAP software modules, as well as their combination options and dependencies. This
includes version numbers, current patch level, and dependencies between landscape components.

For more information about the SAP System Landscape Directory , see
SAP Service Marketplace service.sap.com/sld Media Library SLD User Manual SAP NetWeaver
SAP Help Portal help.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library SAP NetWeaver
SAP NetWeaver Library
SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software
Life Cycle Management System Landscape Directory

To supply data to the SLD that originates from a system other than a J2EE or ABAP system, the executable sldreg is used. The sldreg sends data in
XML format using a predefined DTD. For this purpose it uses an HTTP connection, as shown in the figure below:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 13

On the TREX host, there is an SLD client, which generates an XML file of this type and which registers itself with the SLD server using sldreg.

Prerequisites
After the TREX installation, the SLD client and the associated executable files are located on your TREX host.
The SLD server is running.
You or your SLD administrator have generated the SLD configuration files slddest.cfg and slddest.cfg.key.

The slddest.cfg.key file is only available if the configuration of sldreg was generated using the - usekeyfile parameter.
The user specified in the SLD configuration file slddest.cfg belongs to the DataSupplierLD user role, in order to have permission to send the files
to the SLD.

Generating SLD Configuration Files

In case you generate the SLD configuration files (slddest.cfg and slddest.cfg.key) by yourself you have to know the host, port, user and password of
the SLD server. You generate these configuration files by using the executable files which are located on your TREX host.
1. Set the environment variables required by TREX by executing the following scripts in a command prompt in the directory <TREX_DIR>:
UNIX
Bourne shell sh, Bourne-again shell bash, Korn shell ksh:
. TREXSettings.sh
C shell csh:
source TREXSettings.csh
Windows
TREXSettings.bat
2. Execute the following commands:
Without usekeyfile:sldreg -configure <path>/slddest.cfg
With usekeyfile: sldreg -usekeyfile -configure <path>/slddest.cfg

Copying the SLD Configuration Files to the Global SLD Directory

To configure TREX for the System Landscape Directory (SLD) , you copy the SLD configuration files slddest.cfg and slddest.cfg.key (if available) to
the global SLD directory on your TREX host.
This directory is called <disk_drive>:\usr\sap\<SAPSID>\SYS\global on Windows and /usr/sap/<SAPSID>/SYS/global on UNIX. In the case
of a distributed TREX installation on Windows, all TREX instances use the configuration files for the TREX global file system with first TREX instance as
\\<host_central_instance>\sapmnt\<SAPSID>\SYS\global.

Result
By copying the files slddest.cfg and slddest.cfg.key, you have configured TREX for integration in the System Landscape Directory (SLD).
TREX checks every five minutes whether anything has changed in the TREX system landscape and reports any changes automatically to the SLD server. If
nothing has changed, TREX reports every twelve hours to the SLD server. This allows you to see that this landscape is still active.

Display Results
1. To display the information about TREX systems and services navigate to the screen Content Maintenance
In the initial screen for the System Landscape Directory Development: Content Maintenance
In the initial screen for the System Landscape Directory Administration Content : Content Maintenance
2. In the screen Content Maintenance navigate to Subset and choose All With Instances in the dropdown list.
3. Navigate to Class . In the dropdown list you can display the TREX Services (for example TREX Index Service , TREX Name Service ) and TREX
systems known by SLD.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 13

Information Transferred to the SLD Server

TREX transfers the following information to the SLD server:
Information about naming and version
Software component version (for example, TREX 7.0)
SAP name (for example, TREX)
Version (for example, 7.0)
Information about the TREX servers
Host name, on which the server is running
Port number that the server is using
Type of server, for example, indexserver
Web server URL (instead of the port)
RFC destination of the RFC server (instead of the port)
Information about the TREX instances on individual hosts

System ID
Instance number
Installation directory
Version information for the TREX software

Information about the TREX configuration

Name of the TREX hosts (Hosts) that belong to the TREX system landscape
TREX server roles
Roles of the TREX name server (Name Server Mode)
Possible roles are: 1st, 2nd, 3rd Master Name Server, Slave Server
Use as master index server or master queue server
Roles of the master, slave, and backup index servers
TREX preprocessor mode (Preprocessor Mode)
Information about the TREX installation directory (Base Path)
Services that have been started by the TREX daemon (Services)

Checking Performance Settings for the Operating System

Use
To optimize the performance of TREX when using the released Windows platform, you need to check your Windows configuration and make changes if
necessary.

Optimizing Data Throughput For Network Applications

The Windows installation normally makes caching settings that are optimized for file servers. The operating system then reserves a large part of the main
memory for the caching of files. Since this file-system cache impairs performance when indexing, you ought to change these settings.
1.
2.
3.
4.
5.

Use the secondary mouse button to click on My Network Places on the Windows desktop, and choose Properties.
Use the secondary mouse button to click on the local network connection and choose Properties.
Select the entry File and Printer Sharing for Microsoft Networks and choose Properties.
Select Maximize data throughput for network applications .
Choose OK twice.

Optimizing Performance for Background Processes

Programs such as Microsoft SQL Server and Microsoft Exchange make the setting described below automatically when they are installed. If
you have installed one of these programs, you do not need to make any changes.
The setting is only relevant if TREX is running as a Windows service.
Windows 2000
1.
2.
3.
4.

Use the secondary mouse button to click on My Computer on the Windows desktop, and choose Properties.
Choose the Advanced tab, and then choose Performance Options.
Under Application Response, choose the Background Services field.
Choose OK twice.

Windows Server 2003

1. Use the secondary mouse button to click on My Computer and choose Properties.
2. Choose the Advanced tab, and then choose Settings Advanced.
3. Select Background services under Adjust for best performance of .

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 8 of 13

4. Choose OK twice.

Connecting TREX with an Application

Procedure
TREX can communicate with the application using it by means of an HTTP connection or an RFC connection:
An ABAP application accesses TREX by means of an ABAP client (RFC connection)
As a rule, ABAP applications communicate with the TREX servers by means of the TREX ABAP client using the RFC/SNC protocol. Communication
takes place using an instance of the SAP Gateway and an RFC server.
A Java application accesses TREX by means of a Java client (HTTP connection)
As a rule, Java applications communicate with the TREX servers by means of the TREX Java client using the HTTP or HTTPS protocol. This
communication takes place using a Web server that is enhanced with TREX-specific functions.

There are therefore two procedures for connecting TREX with the application using it:
Connecting TREX with an ABAP Application (RFC Connection)
Connecting TREX with a Java Application (HTTP Connection)

Connecting TREX with an ABAP Application (RFC Connection)

As a rule, ABAP applications communicate with the TREX servers by means of the TREX ABAP client using the RFC/SNC protocol. Communication takes
place using an instance of the SAP Gateway and an RFC server. You configure the RFC connection using the TREX admin tool (stand-alone).

Creating a SAP System User for the TREX Admin Tool (StandAlone)
Use
You must create an SAP user that the TREX admin tool (stand-alone) can use to log on to the SAP system. In addition, the SAP user is required so that the
TREX alert server has permission to regularly test and check the RFC configuration. When doing this, the user can have been created in the default client or in
another client. In this case, make sure that you enter the associated client for the user during the
tool.

configuration of the RFC connection in the TREX admin

The TREX admin tool (stand-alone) is used to configure and monitor TREX. You also use this admin tool to configure the RFC connection between TREX and
the ABAP application that is using TREX. To use the TREX admin tool (stand-alone) to create the RFC destination, the admin tool requires an SAP system
user that you create based on the predefined role SAP_BC_TREX_ADMIN. This user then has the authorization required to configure the RFC connection.

For more information about the SAP_BC_TREX_ADMIN role, see SAP Note 766516.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 9 of 13

Overview of the Permissions Assigned by the SAP_BC_TREX_ADMIN Role

Type and Scope of the Permission

Activity

Explanation

Permission check

Execute

Name of the RFC object to be protected: SYST,

for RFC access

Administration for the
RFC destination

TREX_ARW_ADMINISTRATION
Add or generate, change, display, delete, extended
maintenance

Check on the transaction code at transaction launch

Type of entry in RFCDES: Start of an external program

using TCP/IP
Transaction code: SM59, TREXADMIN,
TREXADMIN_AUTH

Administrating TREX

Change, display, execute

ABAP: Program run checks

Schedule programs for background processing,

execute ABAP program, maintain variants for and
execute ABAP program

ALV standard layout

Maintain

Application log

Display, delete

More Information
Configuring and Administrating the RFC Connection
Configuring the RFC Connection in the TREX Admin Tool

Procedure
Create an SAP system user for the TREX admin tool (stand-alone) and assign the SAP_BC_TREX_ADMIN role to this user.
1. Launch transaction SU01 (user maintenance) or choose Administration System Administration User Maintenance User in the SAP menu .
The User Maintenance : Initial Screen appears.
2. Enter a new user name and choose Create .
3. On the Address tab page, enter the personal data for the user.

For more information about creating users, see

Creating and Maintaining User Master Records.
4. On the Roles tab page, assign the SAP_BC_TREX_ADMIN role and thus the permission to access the SAP system to the SAP system user for the
TREX admin tool (stand-alone).

Result
This user for the TREX admin tool (stand-alone) now has the authorization required to configure the RFC connection.

Determining the SAP System Connection Information

Use
The TREX admin tool (stand-alone) can connect to an SAP system in two ways.
Through a specific application server of the SAP system (variant A)
Through the message server of the SAP system (variant B)
This variant uses the load-balancing function for the SAP system. The message server assigns the request from the TREX admin tool to any application
server.
Depending on the variant used, the TREX admin tool requires different connection information for the SAP system. You must determine the connection
information and specify it later in the TREX admin tool.

SAP recommends using variant B. Variant A has the disadvantage that the connection does not work if the application server is not available.

Procedure
1. Open the SAP Logon.
SAP Logon is the program that you use to log on to an SAP system.
2. Note the following connection information:
Connection Setup Type

Required Connection Information

Through an application server (variant A)

SAP system ID (SID)

System number
Application server host name

Through the message server (variant B)

SAP system ID (SID)

Logon group, such as PUBLIC

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 10 of 13

PUBLIC
Message server host name

Configuring the RFC Connection in the TREX Admin Tool

Use
You work through the steps below using the TREX admin tool (stand-alone).

Configuration of the RFC connection with the TREX admin tool (stand-alone) is only available as of SAP Basis Component SAP_BASIS 6.20
SP58, 6.40 SP16, and 7.0 SP6. If you are using TREX with an SAP system based on an earlier support package, you have to configure the
RFC connection manually as described in the SAP NetWeaver 04 Installation Guide for Search and Classification (TREX) 6.1. You can find
this guide on the SAP Service Marketplace at service.sap.com/instguides SAP NetWeaver Released 04 Installation Cross-NW
Installation Guide Search and Classification TREX 6.1.

Creating a Connection
1. On the RFC: Current tab page in the Landscape: Connectivity window, choose the Create Connection function.
2. Choose connection type A or B. Specify the connection data for the SAP system (see Determining the SAP System Connection Information).
3. Specify the SAP system user, the associated password, and the client that the TREX admin tool is to use to log on (see Creating a SAP System User for
the TREX Admin Tool (Stand-Alone)).

If the SAP system user in question exists in the default client, you do not need to specify the client.

Creating an RFC Destination

1. To do this, use the Create: RFC Destination (SM59) function on the RFC: Current tab page in the Landscape: Connectivity window.
2. Enter the following parameters:
Field

Entry

SAP System

SAP system that you want to set up the connection to.

The list contains all SAP systems that you have registered using Create
Connection .

RFC Destination

Name of the RFC destination.

Description

Meaningful description of the purpose

The program ID determines under which name the TREX RFC server registers with the SAP gateway. The program ID must be unique for each SAP
gateway. The TREX admin tool ensures this by generating the program ID.
3. Decide which SAP gateway you want to use. You have the following options:
Option

Comment

Gateway local

Use local SAP gateways for the application servers.

(Default setting)
Gateway central

Use the central SAP gateway.

We advise against using a central SAP gateway for distributed TREX systems.
The central SAP gateway is a single point of failure.
If you choose this option, enter the following additional parameters:

Host name (with domain name if necessary) or the IP address of the host
on which the gateway is installed.
Name of the SAP gateway in the form sapgw<instance_number>

We advise against creating the RFC destination directly in the SAP system. The name of the RFC destination and the program ID must satisfy
certain naming conventions. The TREX admin tool ensures that these are fulfilled.
If you nevertheless create the RFC destination directly in the SAP system, note the following:
We recommend starting the name of the RFC destination with TREX_.
Choose the activation type Registered Server Program .
Choose a program ID that is unique for the SAP gateway used.
Use the RFC Destinations function to register the RFC destination in the TREX admin tool.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 11 of 13

Completing the RFC Configuration

1. On the RFC: Current tab page in the Landscape: Connectivity window, choose the Connect Admin Tool function.
The TREX admin tool creates the connection to all SAP systems that are known to it. Because the RFC configuration is still incomplete, the configuration
status is
yellow or
red.
2. Choose Repair All .
The TREX admin tool completes the RFC configuration and starts the TREX RFC server.
This can take several minutes. During this time, the configuration status remains
yellow or
status changes to
green.

red. After completion of the configuration process, the

Do not choose Repair All several times in quick succession. This would trigger the configuration process more than once and delay it.
3. Check the progress by choosing Refresh to update the display.

Connecting TREX with a Java Application (HTTP Connection)

As a rule, Java applications communicate with the TREX servers by means of the TREX Java client using the HTTP or HTTPS protocol. This communication
takes place using a Web server that is enhanced with TREX-specific functions. The TREX Java client needs to know the address of the TREX name server in
order to communicate with the TREX servers. You specify the address of the TREX name server, and, in the case of a distributed TREX installation, of the
TREX backup name server, in the SAP NetWeaver Administrator.

Specifying the Address of the TREX Name Server

Use
TREX provides APIs (Application Programming Interfaces) for the languages Java and ABAP, which allow access to all TREX functions. The Java interface
(TREX Java client) is part of the SAP Web AS Java as TREX service . The TREX Java client needs to know the address of the TREX name server in order
to communicate with the TREX servers.
The following procedure describes how you determine the TREX name server address and how you specify it in the SAP NetWeaver Administrator .

The TREX Java client communicates with the TREX server by HTTP and TCP/IP. Make sure that the TCP port that the name server uses is
open.

Procedure
You have to specify the address of the TREX name server in the SAP NetWeaver Administrator by naming the following values
<host_name_of_trex_host>:<name_server_port>:
<host_name_of_trex_host>: name of the host on which TREX is installed and where the TREX name server runs.
<name_server_port>: port of the TREX name server
1. You can determine the TREX name server address in two ways:
a. Start the TREX admin tool (see Starting the TREX Admin Tool) and determine the address of the name server using Landscape
topology globals all_masters .

Tree

For example: mytrexhost:34801

b. Determine the port of the TREX name server by means of the following rule: <name_server_port>: 3<instance_number>01

The value <instance_number> signifies the TREX instance number which had been specified during the TREX installation:
Installation directory for TREX
On UNIX /usr/sap/<sapsid>/trx<instance_number>

On Windows <disk_drive>:\usr\sap\<SAPSID>\TRX<instance_number>

The value for <host_name_of_trex_host> you know from the host where TREX is installed (mytrexhost).
2. Use the user <j2eeadm> to log onto the host on which the Application Server Java is running.
3. Start the SAP NetWeaver Administrator and log on to the AS Java .

For more information about using and starting the SAP NetWeaver Administrator , see
SAP NetWeaver Administrator and SAP Help
Portal help.sap.com.
4. Navigate to Configuration Management Infrastructure Management Java System Properties.
5. In the new screen go to the tabulator Services in the screen area Details and type in trex.service to filter the available services .
6. In the Extended Details area under the tabulator Properties enter the address of the TREX name server into the parameter nameserver.address:
tcpip://<host_name_of_trex_host>:<name_server_port>

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 12 of 13

You enter only the host name or the host name and the domain depending on your network environment.

tcpip://mytrexhost:34801 or tcpip://mytrexhost.mydomain:34801

The address of the TREX name server must be configured for all server processes of the cluster. Otherwise the connection between the AS
Java and TREX cannot be established.
7. In case of a multiple host scenario for a distributed TREX landscape you enter the addresses of the TREX backup name servers in the parameter
nameserver.backuplist. Specify the address of the TREX backup name servers, separated by comma in the format:
tcpip://<host1>:<port1>,tcpip://<host1>:<port1>,

For a TREX single-host installation you do not need to specify backup name servers.
8. Save your changes and confirm the restart of the service.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 13 of 13