Software Logistics standardizes and automates software distribution and maintenance as well as test procedures for complex software landscapes and various software development platforms. These functions support your project, development, and application support teams.
Software Logistics aims to implement a consistent, cross-solution change management that provides several procedures for maintenance, global rollouts, and localization, as well as open integration with products offered by third-party organizations.
New TREX releases are always tested internally using a predefined test package with a standard test landscape and with verifiable test data. In particular, the handling of mass data (mass tests), load restrictions (stress tests), and the performance of TREX are checked. The test package calls test atoms in the form of Python scripts that test the basic functionality of TREX and are stored in the following directory:
● UNIX
/usr/sap/<sapsid>/TRX<instance_number>/exe/python_support
● Windows
<disk_drive>:\usr\sap\<SAPSID>\TRX<instance_number>\exe\python_support
When you have installed TREX, you execute the Python script runInstallationTest.py that is used to test the basic TREX functions. This script calls a subset of TREX test atoms to check the functional correctness of TREX. If the Python script is executed successfully, you know that TREX has been installed properly, the configuration files contain the necessary entries, and the TREX servers are running.
On the TREX side, the data exists in the form of indexes that are built from the original data in the application using TREX. Therefore, TREX indexes are redundant copies of the application data. The TREX indexes can be restored from the original data at any time. There are no data transports for TREX that are comparable with the usual procedures for SAP systems and that you could use to transport TREX data and configuration settings from a development system through a consolidation system to a production system. However, it is possible to use Python scripts to copy TREX indexes and configuration files between servers. There are customer-specific solutions that make transports of this type possible for your specific situation. In the case of a data transport of this type, you must always copy the application data consistently with the TREX data. A procedure of this type is expressly not recommended by TREX and therefore not supported.
The documentation below supports you in the installation, upgrade, and migration of TREX.
Make sure that you use the current version of the TREX guides. You can find them on the SAP Service Marketplace at service.sap.com/instguidesNW70
Guide |
Description |
SAP NetWeaver 7.0 Search and Classification (TREX) Multiple Hosts installation guide |
For the installation and configuration of distributed TREX systems |
SAP NetWeaver 7.0 Search and Classification (TREX) Single Host installation guide |
For single-host installation of TREX |
Support Package Stack Guides – SAP NetWeaver |
For updates to a new support package stack |
In a distributed TREX system, you perform an update on the TREX host on which the central TREX instance and the global file system were installed. In this case, the central TREX instance selected is updated first and then once TREX is restarted, all TREX dialog instances in a TREX system landscape are updated automatically by means of the replication of the current binaries.
The following SAP Notes contain current installation information and corrections to the installation documentation.
Make sure that you use the current version of the SAP Notes. You can find SAP Notes on the SAP Service Marketplace at service.sap.com/notes.
Relevant SAP Notes
SAP Note |
Title |
Comment |
843360 |
Installing TREX 7.0 |
Contains current information on installation of SAP NetWeaver 7.0 TREX |
802987 |
TREX 7.0: Central Note |
Central SAP Note on SAP NetWeaver 7.0 TREX |
492305
|
INST: SAP J2EE Engine / Dialog Inst. / Gateway Inst. 6.20
|
Relevant for an installation with an RFC connection: Contains current information on the SAP Gateway installation. |
658052
|
TREX 6.0/6.1/7.0: Additional Information About TREX ABAP Client
|
Relevant for an installation with an RFC connection: Contains recommendations for using the queue server and information on which application uses which version of the ABAP client. This information is relevant for configuration steps after the TREX installation. |