TREX is based on a client/server architecture. The client software is integrated into the application that uses the TREX functions, and allows communication with the TREX servers. The TREX servers execute the requests of the clients: They index and classify documents and respond to search queries.
Example:
Installtion guide for SAP NetWeaver 2004s Standalone Engine Search and Classification (TREX) Single Host
Note 802987 - TREX 7.0: Central Note
Note 1450091 - TREX 7.00: Revision 50 ( for Trex 7.00.50.00)
export DISPLAY=<jump host>:143.0
export SAPINST_JRE_HOME=/usr/bin
[root@trexhost]# export TMP=/tmp;export TEMP=/tmp;export TMPDIR=/tmp
From root user run the SAPINST
Complete the SAPINST Process .
You can determine the TREX name server address in two ways:
Make sure all services are green in Trexadmin tool.
You have to specify the address of the TREX name server in the SAP NetWeaver Visual Administrator by naming the following values <host_name_of_trex_host>:<name_server_port>
If a Java application communicates with TREX, you configure the TREX Java client, which is integrated as a TREX service in the J2EE engine. You also check the client-side proxy settings.
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 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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |