Checklists
Purpose
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 a TREX global file system (see the TREX installation guide) |
|
|
|
On all TREX hosts |
|
Install a TREX dialog instance (see the TREX installation guide) |
|
|
|
Only Windows: Define a network drive for the central TREX data directory |
|
Start TREX |
|
On a future master name server |
|
|
|
With an RFC connection: On all TREX hosts and in the SAP system |
|
|
|
With 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 |
|
|
|
With an RFC connection: On all server blades and in the SAP system |
|
|
|
With an HTTP connection: On the J2EE Engine |
|
Individual hosts with decentralized data storage
! |
Action |
|
On a future master name server |
|
Install a central TREX instance (see the TREX installation guide) |
|
On all other TREX hosts |
|
Install a TREX dialog instance (see the TREX installation guide) |
|
On all TREX hosts |
|
Start TREX |
|
On a future master name server |
|
|
|
With an RFC connection: On all TREX hosts and in the SAP system |
|
|
|
With an HTTP connection: On the J2EE Engine |
|