You work through the steps below using the TREX admin tool (standalone).
Configuration of the RFC connection with the TREX admin tool (standalone) 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 SAP Service Marketplace service.sap.com/instguides: .
If the SAP system user in question exists in the default client, you do not need to specify the client.
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 Gateway. The program ID must be unique for each Gateway. The TREX admin tool ensures this by generating the program ID.
Option | Comment |
---|---|
Gateway local (default setting) |
Use local SAP gateways for the application servers. |
Gateway central |
Use central Gateway. Note
We advise against using a central Gateway for distributed TREX systems. The central Gateway is a single point of failure. If you choose this option, enter the following additional parameters:
|
If you nevertheless create the RFC destination directly in the SAP system, note the following:
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.
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 red. After completion of the configuration process, the status changes to green.
Do not choose Repair All several times in quick succession. This would trigger the configuration process more than once and delay it.