Update installation of openFT

If openFT V11.0 or V12.0 is already installed, an update installation is performed.

Points to observe preparatory to an update installation

During an update installation, the following actions are carried out for all active instances including the standard instance:

• The log file is deleted. Therefore you should evaluate the log records before performing the update installation.

• Any running openFT-Script requests are aborted during installation. All old, aborted openFT-Script requests are not regarded as being restartable in the new openFT version. You should therefore complete all running openFT-Script requests before carrying out an update installation.

• Existing trace files, if any, and diagnostics files are deleted.

If you wish to continue using openFT instances that have been deactivated using ftdeli, you should activate them before the update installation using ftcrei. The corresponding instance file trees are then automatically updated during installation. If you do not do this, you must update these instances after installation using the ftupdi command (see the manual "openFT (Unix and Windows systems) - Command Interface").

Tasks required of the system administrator

1. Install openFT from the data medium.

2. During installation, you are prompted to enter the license key.

Following an update installation, the asynchronous openFT server for the standard instance is started automatically, i.e. the operating parameter option Start Asynchronous Server Automatically is activated in the openFT Explorer. To access this option, choose the Operating Parameters command in the Administration menu and go to the General tab. This option is deactivated for the other instances. You must therefore activate this option in these instances if you always want the associated asynchronous openFT server to be started automatically.

Steps performed automatically

The following steps are performed automatically for an update installation:

• openFT-Script requests are cancelled.

• In the case of an openFT V10.0 update installation, the default TNS entries for openFT are handled as follows:

  • Default TNS entries from older openFT versions < V10.0 that are no longer required are deleted

  • Missing required default TNS entries are created.

  • Existing required default TNS entries remain unchanged.

• The language setting from the previous version is used. The instance directories of currently existing instances including the standard instance are updated, i.e.:

  • The log file is deleted.

  • During this, the following configuration data are used:

    • Operating parameters (the operation CMX with remains activated)

    • Instance identification

    • partner list entries

    • Admission sets and profiles:

    • Key pair sets:

    • Configuration data for central administration (in the case of an update from V11.0).

If it is necessary to reboot the computer on an update installation then the instance update is not performed until after the reboot. If errors occur, a ftupdi-instance.log file with corresponding error messages is created in the %ProgramFiles%\openFT directory. After each update installation with reboot you should check whether there are ftupdi-instance.log files in the %ProgramFiles%\openFT directory. If so, the instances must be updated manually using the ftupdi directory command. The associated ftupdi-instance.log file can be deleted after a manual update.

As of openFT version 12.1C20, there are two additional key pairs with lengths 3072 and 4096. They are generated after the update installation is complete as soon as the instance is running for the first time.