Installation in an alternative root directory (Solaris)

On the Solaris platform, openFT permits installation in an alternative root directory. This means that the files and directories of the openFT package are not installed in the root directory of the system that is currently running but in another directory that already contains an operating system environment and from which the system will subsequently be booted.

Installation in an alternative root directory is essential if support for live upgrade procedures is required. In the case of live upgrade procedures, the root file system is duplicated to an alternative root file system. The software (operating system update and additional software packages) is then installed in the alternative root file system from which the system is subsequently booted.

Variable openFT files

The variable openFT files are installed in the directory /var/openFT. It is not possible to work with a /var directory that is shared between the root directory and the alternative root directory.

The administrator is responsible for synchronizing the variable openFT files between the root file system and the alternative root file system, i.e. the administrator must synchronize the variable openFT files before starting the new system.

Installation of openFT

In the case of an update installation, the alternative root directory already contains an openFT version V11.0 or V12.0, or, if a correction version is to be installed, an openFT Version V12.1.

As of openFT version v12.1C30 during installation, you are asked to enter the license keys:

• If you specify a valid basic license key then the basic functionality of openFT will be enabled (openFT protocol, FTADM protocol and FTAC functionality). The optional license keys for the FTAM and FTP protocols are then queried. If you enter a valid license key for an optional protocol then this protocol is also enabled. You can skip this dialog box if you do not possess a valid key for FTP or FTAM.
  If you enter a valid license key for a special version (e.g. CL or FTAM-CL version) then you will not be asked to enter a license key for FTAM and/or FTP because the supported function scope is already present in the special version.

• If you do not enter a license key then openFT runs with full functionality as a demo version for 30 days. This demo version may only be used for evaluation purposes!

  Following installation, you can enter openFT license keys at any time using the openFT Explorer (Administration - License Administration) or the ftaddlic command.

Proceed as follows:

1. Install the openFT V12.1 product software in the alternative root directory.

   For this purpose, change to the mounted directory and start the following procedure:

   sh install.ft –r=<alternative root directory>

   Example:

   To install openFT in the directory /altroot invoke the following command:

   sh install.ft –r=/altroot

   When you do this, the fixed files and directories in the openFT package are installed in the alternative root directory, e.g. /altroot/opt/openFT.

2. The following steps are necessary following a new installation or an update installation in order to generate the variable openFT files (new installation) or convert them to openFT V12.1 format (update installation):

   1. Boot from the alternative root directory without starting openFT.

      The automatic start-up of openFT via SMF is not yet activated.

   2. Call the shell procedure ftconfig:

      /opt/openFT/bin/ftbin/ftconfig

      openFT is now fully installed.

   3. Start openFT.

Following a correction installation, openFT is automatically configured and started the first time the new system is started up. In this case, it is not necessary for the administrator to call the shell procedure ftconfig, or start openFT.

Restrictions applying to an update installation

After an update installation, the following restrictions apply:

If you switch back to the original root file system then it is not possible to synchronize the variable openFT files because configuration files updated with openFT V12.1 cannot be converted back to an earlier version. This means that openFT requests and settings that have been made in the alternative root file system as well as new log records, trace files, diagnostics records etc. will be lost.