Hardware, Software, and Other Requirements
This section lists the requirements that are unique to distributed systems. These hardware requirements relate to production systems.
| Requirement Type | Requirement | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CPU |
For one index server per TREX instance:
With two index servers per TREX instance: At least 4 CPUs. The supported processors are listed in the TREX installation guide. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
RAM |
At least 2 GB per CPU |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Network connection |
At least 100 Mbit |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
With centralized data storage: Connection to the file server. |
At least 1 Gbit Note
SAP recommends that you define a separate sub network. Caution
All TREX hosts must be identical as regards the number of CPUs, RAM, and network connection. Decentralized Data Storage: Disk Space for TREX Data Note
The formulas specified here are approximate and do not return exact values. Required disk space on one master host
Note
We strongly recommend that you place the master indexes and the index snapshots on different hard disks. This improves performance when indexing and replicating indexes. Required disk space per slave host
Caution
The hard disk capacity and performance must be identical on master and slave hosts. Tip
You have a document set size of 50 GB of HTML/text documents or 50 GB of mixed documents. The following table presents the required space on the master host.
The following table presents the required space on each slave host.
Centralized Data Storage: Disk Space for TREX Data Note
The formulas specified here are approximate and do not return exact values. Required disk space on the file server
Note
You do not need additional disk space for the slave index. The slave index servers use one of the index snapshots as their slave index. Tip
You have a document set size of 50 GB of HTML/text documents or 50 GB of mixed documents. This results in the following disk requirements on the file server:
Disk Space for TREX Software and SAPinst As for a single host system (see the TREX installation guide). Software Requirements
The software requirements in the TREX installation guide are also valid. Operating System User and Permissions The installation automatically creates the operating system user SAPService<SAPSID>. In the case of a TREX system with centralized data storage, you must ensure that the user SAPService<SAPSID> has full access permission for the TREX data directory on the file server. Note the following:
In the case of a TREX system with decentralized data storage, there are no special requirements regarding access permission. System ID During the TREX installation, you enter a three digit system ID, for example, TRX. You must use the same system ID for all TREX instances that you want to group together as a distributed system. TREX Instance Number SAP recommends that you use the same instance number for all TREX instances in order to simplify administration. You define the instance number during the TREX installation. There is only one TREX installation in a blade system with centralized program storage. The instance number is the same for all server blades. During the installation of TREX you have to choose an instance number that is still free on all the server blades on which TREX is going to run. TREX Daemon You only have to change the configuration of the TREX daemon on the individual hosts under certain circumstances. These circumstances are described in this documentation. Otherwise, you can keep the standard configuration, even if the TREX daemon starts processes that are not used. Such processes do not use up system resources and therefore do not affect performance. If you keep the standard configuration it is easy to change the roles of the hosts. Tip
By default, a queue server runs on each host. The queue server has no function on a slave host. It is not used. You do not need to make configuration changes to the TREX daemon on the slave host. Connecting TREX to More Than One Application In principle, you can connect one TREX system to more than one application. Note the following:
|