CMX and openFT can also be installed unattended using the msiexec command (Windows Installer). Please note the following:
Installation must be started from a console with administrator rights, i.e. the installation must either be performed by the administrator or the console must have been started with Run As Administrator with user account control activated. Otherwise you will not be authorized to perform the installation!
If you want to work in "operation with CMX" mode then you should install CMX before installing openFT. This automatically generates the default TNS entries for openFT.
You use msiexec to install the MSI installation packages openFT.msi and/or PCMX-32.msi. Both of these are located in the directory openFT\Unattended_installation on the product CD.
When calling msiexec, specify the relevant MSI file as an argument.
Possible other Windows Installer parameters:
ADDLOCAL:
ADDLOCAL is used to specify which optional features are installed. Possible value is for ADDLOCL is SNMP.
ADDLOCAL SNMP means that the openFT SNMP subagent is installed in addition to openFT. For this to be possible, the Microsoft SNMP service must be installed first, see section “Installation of the SNMP subagent”.
If ADDLOCAL is not specified then only the openFT protocol is installed whereas SNMP support is not installed.
openFT can only use transfer protocols for which a valid license key is available (see the openFT properties LICENSEKEY, FTAMLICENSEKEY and FTPLI-CENSEKEY).
TRANSFORMS:
The German variant of openFT can be set by specifying the TRANSFORMS:de parameter. For details on setting the language see section “Switching the language interface”.
openFT properties:
LICENSEKEY:
A valid openFT license key must be specified for the LICENSEKEY parameter. 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 the openFT license key at any time using the openFT Explorer (Administration - License Administration) or the ftaddlic command.
The LICENSEKEY consists of five subkeys of five characters each and separated from one another by a minus sign.
Example:
12345-12345-12345-12345-12345
FTAMLICENSEKEY:
The specification of FTAMLICENSEKEY is optional.
A valid license key for the FTAM protocol must be specified for FTAMLICENSEKEY. The specification of FTAMLICENSEKEY is only of use if you have entered a license key for a server version of openFT in LICENSEKEY.
If you have not specified a license for the FTAM protocol, you should not specify FTAMLICENSEKEY. In this case, the FTAM protocol cannot be used. Following installation, you can enter the license key for the FTAM protocol at any time using the openFT Explorer (Administration - License Administration) or the ftaddlic command.
The FTAMLICENSEKEY consists of five subkeys of five characters each and separated from one another by a minus sign.
Example:
54321-54321-54321-54321-54321
FTPLICENSEKEY:
The specification of FTPLICENSEKEY is optional.
A valid license key for the FTP protocol must be specified for FTPLICENSEKEY. The specification of FTPLICENSEKEY is only of use if you have entered a license key for a server version of openFT in LICENSEKEY.
If you have not specified a license for the FTP protocol, you should not specify FTPLICENSEKEY. In this case, the FTP protocol cannot be used. Following installation, you can enter the license key for the FTP protocol at any time using the openFT Explorer (Administration - License Administration) or the ftaddlic command.
The FTPLICENSEKEY consists of five subkeys of five characters each and separated from one another by a minus sign.
Example:
32154-32154-32154-32154-32154
INSTALLDIR:
The INSTALLDIR parameter enables you to specify the installation directory for openFT, see also section “Installation of openFT”.
The INSTALLDIR parameter can also be specified with the PCMX-32.msi package for unattended CMX installation.
By default, openFT is installed in the directory %ProgramFiles%\openFT.
You must not specify network drive paths or UNC paths as the installation path (INSTALLDIR).
openFT must be installed on a local hard disk.
The maximum length of the selected installation directory is 110 characters. If you specify a longer installation directory then installation is rejected.
It is recommended that you omit the INSTALLDIR parameter. In this case, the default installation path is used.
Examples
You start unattended installation of CMX without user interaction with
msiexec /i PCMX-32.msi /qnYou start unattended installation of the German language version of openFT (without user interaction) in the default directory %Program Files%\openFT with
msiexec /i openFT.msi TRANSFORMS=:de /qnEnter the following command to start unattended installation without user interaction of the German language version of openFT including SNMP in the default directory:
msiexec /i openFT.msi ADDLOCAL=SNMP TRANSFORMS=:de /qnFor the unattended installation, without user interaction, of openFT with SNMP in German in the default directory including specification of the openFT and optional FTAM license keys, enter the following command:
msiexec /i openFT.msi ADDLOCAL=SNMP LICENSEKEY=12345-12345-12345-12345-12345 FTAMLICENSEKEY=54321-54321-54321-54321-54321 TRANSFORMS=:de /qn
In the case of unattended installation, the exit code of msiexec.exe indicates whether installation was successful or not. To use this facility, start msiexec as follows:
start /wait msiexec /l*vx install.log /i openFT.msi ADDLOCAL=SNMP LICENSEKEY=12345-12345-12345-12345-12345 FTAMLICENSE=54321-54321-54321-54321-54321 TRANFORMS=:de /qn /norestart
Directly after completion of the msiexec command, use echo %ERRORLEVEL% to query the exit code:
0 | Installation successful, it is not necessary to restart the computer |
3010 | Installation successful, it is essential to restart the computer |
All other exit codes (e.g. 1603) indicate an error during installation, for example the specification of an invalid license key or an invalid installation directory.
If an error occurs then the reason can be determined via the optional installation log install.log.
In the example above, this logging was activated using the /l*vx install.log option in the msiexec command at the start of installation. At the end of the logged installation sequence and before the concluding list of properties, it is usually possible to find the error message and a description of the error that caused the installation operation to be aborted.
A detailed description of the msiexec command together with a complete list of the possible exit codes can be found on the Microsoft web site.