Configuring SAP NetWeaver Enterprise Search for the Customer Network 
In this step, you modify SAP NetWeaver Enterprise Search to suit your system landscape to allow load balancing using your SAP message server and user management using your LDAP server.
Prerequisites
You have access to at least one other SAP system at operating system level to copy /etc/services from an existing SAP installation because this file contains information on the gateway configuration for the particular customer landscape. In the case of a Windows system, this file is located at c:\WINDOWS\system32\drivers\etc\services.
Procedure
Registering the Existing SAP Message Servers
To activate load balancing, for example when searching ERP objects, the message servers in your system landscape must be known to SAP NetWeaver Enterprise Search. With load-balancing, part of the load can be shifted to the existing back-end systems.
Copy the content of an existing /etc/services file, which contains information on the gateway configuration for the particular customer landscape, from an existing SAP installation to the /etc/services file on all blades of SAP NetWeaver Enterprise Search.
Registering an LDAP Server
If you are using an LDAP server for user management or for file searching with authorizations, you must register this LDAP server on the ABAP system once you have connected it to the ABAP server.
On the master blade, create a file called reg_info in the /usr/sap/<SAPSID>/<INSTANCE>/data/ directory.
NoteFor example, DVEBMGS00 could stand for <INSTANCE> here.
End of the note.Enter the following lines in the file:
TP=<LDAP_program> HOST=<central_ABAP_instance> NO=1 ACCESS=<central_ABAP_instance>
TP=<TREX_program> HOST=<central_TREX_instance> NO=1 ACCESS=<central_ABAP_instance>
Note
The program names must be the same as in the corresponding RFC destinations (transaction SM59). The TREX RFC destination has the name TREX_RFC and the destination to the LDAP server usually begins with LDAP. Both destinations are of type TCP/IP (T).