There are two methods for indexing:
With queue server
The RFC server sends the documents to be indexed to the queue server. The queue server collects the documents and transmits them to the index server according to the conditions defined in the queue parameters. The actual indexing takes place on the index server.
Without queue server
The RFC server sends the documents to be indexed to the index server.
The most suitable configuration depends on the application. The version of the TREX ABAP client determines whether you can configure usage of the queue server in the file TREXRfcServer.ini. SAP Note 658052 contains information on which configuration is most suitable for each application and whether you have to activate the usage of the queue server in the file TREXRfcServer.ini.
If you have to activate the usage of the queue server, edit the configuration file <TREX_DIR>/<host_name>/TREXRfcServer.ini.
In the section [CONNECTION], set the parameter USE_QUEUESERVER to YES:
The changes take effect when you next start the RFC server. The RFC server is automatically started by the TREX daemon and/or by Gateway.
If you use the queue server, check the queue parameters regularly and set them according to your requirements. Make sure that you configure the intervals at which the queue server is to transmit documents to the index server. The settings that are suitable depend on how often documents are to be indexed, and how quickly you want them to be available for the search.
You can configure queue parameters using the Python version of the TREX administration tool, for example. For more information, see SAP Library at help.sap.com.