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 requests are deleted from the request queue unconditionally. If any follow-up processing was specified with the option -lf= in the submitted request, this is completed in the process.
Existing trace files, if any, diagnostics records and console commands 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
Install openFT from the data medium.
On a system in which the openFT installation takes place in a dialog, you need to answer questions during installation asking you if you have a valid openFT-FTAM license and a valid openFT-FTP license. Only activate this option if you have a valid license for openFT-FTAM or openFT-FTP! Depending on the answers openFT-FTAM and/or openFT-FTP may or may not be installed.
These questions are not asked on Solaris and Linux systems. If you want to use the FTAM or FTP functionality on these systems, then you must activate openFT-FTAM and/or openFT-FTP via the command /opt/bin/ftaddlic <license string> after installing openFT. See also the manual "openFT (Unix and Windows systems) - Command Interface".
- As of openFT version V12.1C30, openFT license keys (one for the openFT protocol and optionally one each for the FTAM and FTP protocol) can be entered at any time after installation using the openFT Explorer (Administration - License management) or the ftaddlic command.
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! If you have made modifications in the old startup and shutdown files, then you must also
make them in the new startup and shutdown files in the case of an update installation under Linux, HP-UX or AIX
make them in SMF in the case of Solaris, see section “Solaris SMF”.
Steps performed automatically
The following steps are performed automatically for an update installation:
Running openFT processes and the openFT Explorer are terminated.
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. On Linux platforms, however, the openFT man pages are installed in both German and English, i.e. users see the man pages in the language set for their login session.
The instance directories of currently existing instances including the standard instance are updated, i.e.:
The log file is deleted.
The old, instance-specific startup and shutdown files are backed up under /var/openFT/instance/etcinit/openFTinst.old (instance = name of the instance). The new instance-specific startup and shutdown files are then read in on Linux, HP-UX and AIX platforms. On the Solaris platform, SMF is supported, see section “SolarisSMF”. As a result, no further startup or shutdown files are created.
During this, the following configuration data are used:
Operating parameters (the operation CMX with remains activated)
Instance identification
partner list entries
The FTAM catalog
Admission sets and profiles
Key pair sets
Configuration data for central administration
openFT is started for those instances, for which it was started before the installation (not applicable on HP systems).
The system searches for a suitable Java executable and this is notified to openFT. If no such system is found then you proceed as described in section “Installation of openFT”.