The procedure depends on the following:
The type of data storage you use (centralized or decentralized)
The hardware you are using (individual hosts or blade system)
Below are the checklists for the different scenarios.
Individual hosts with central data storage
Action |
|
|
On the file server: |
|
Install the TREX system (first TREX instance + global file system) (see the TREX installation guide Single Host) |
|
|
|
On all TREX hosts |
|
Install another TREX instance (see Installing a TREX Instance on Another Host). |
|
|
|
|
|
Start TREX |
|
On a future master name server |
|
|
|
For an RFC Connection: On all TREX hosts and in the SAP system |
|
|
|
For an HTTP Connection: On the J2EE Engine |
|
Blade system with central program and data storage
Action |
|
|
On the file server: |
|
Install TREX (see the TREX installation guide Single Host) |
|
|
|
On all server blades on which TREX is to run |
|
Start TREX |
|
On a future master name server |
|
|
|
For an RFC Connection: On all server blades and in the SAP system |
|
|
|
For an HTTP Connection: On SAP NetWeaver AS |
|
Individual hosts with decentralized data storage
Action |
|
|
On a future master name server |
|
Install the TREX system (first TREX instance + global file system) (see the TREX installation guide Single Host) |
|
On all other TREX hosts |
|
Install another TREX instance (see Installing a TREX Instance on Another Host). |
|
On all TREX hosts |
|
Start TREX |
|
On a future master name server |
|
|
|
For an RFC Connection: On all TREX hosts and in the SAP system |
|
|
|
For an HTTP Connection: On SAP NetWeaver AS |
|