Show TOC

Activating the Configuration Clones for Server BladesLocate this document in the navigation structure

Use

You can install TREX on a blade system so that the TREX data and program files are stored only once on the file server and are used by all server blades. Every server blade on which TREX is running needs its own configuration files.

You use a Python script to duplicate the profile files and the configuration to all server blades in your TREX landscape so that each server blade receives its own configuration files.

You do this in the following steps:

Initial Installation of TREX on a Central File Server

  1. Mount the central file server.

    Example

    /mnt/myfileserver

    Note

    SAP recommends that you enter the directory /mnt/myfileserver in the configuration file /etc/fstab, so that the directory is automatically remounted when the host is started again.

  2. Create a subdirectory, for example, <SAPSID> for the directory /mnt/myfileserver.

    Example

    /mnt/myfileserver/<SAPSID>

  3. Generate symbolic links ( symlinks) that link from the directories /usr/sap/<SAPSID> and /sapmnt/<SAPSID> to the directory mnt/myfileserver/<SAPSID>.

  4. Install TREX.

  5. Check whether TREX has been started and, if necessary, start TREX.

Duplicating Profile Files and the Configuration to Server Blades

  1. Log on with the root user.

  2. Mount the central file server.

    Example

    /mnt/myfileserver

  3. Generate symbolic links ( symlinks), which link from the directories /usr/sap/<SAPSID> and /sapmnt/<SAPSID> to the directory mnt/myfileserver/<SAPSID>.

  4. Switch to the TREX directory /usr/sap/<SAPSID>/TRX<instance_number>.

  5. Set the environment variables required by TREX by executing the following Shell scripts.

    • Bourne shell sh, Bourne-again shell bash, Korn shell ksh:

      .TREXSettings.sh

    • C shell csh:

      source TREXSettings.csh

  6. Execute the Python script cloneInst.py:

    python exe/python_support/cloneInst.py

Result

The Python script cloneInst.py executes the following actions on the server blades that have been added:

  • Create the same users on the added server blade as on the initial server blade

  • Copy and modify the SAP profile files from the initial server blade

  • Copy and modify the configuration files from the initial server blade

  • Extend the directories /etc/init.d and /usr/sap/sapservices

  • Start TREX