This article explains how to install Talend products using the silent or unattended installation method, which involves the creation of an options file.
The installation of Talend products is usually performed using the graphical mode installer, or on Linux, the text mode installer. There are, however, situations where an unattended or silent installation is desirable, and this document details this process.
See Installation modes of Talend Installer and Talend Studio Installer for more information about the different modes that the Talend installer can run in.
Just like the graphical installer, the silent installer can only be run on the target server where Talend is installed. There is no concept of a remote installation.
There is no option to accept or decline the license agreement—agreement can only be implicit.
All options in the options file are case sensitive: licensefile is not the same as licenseFile. Some options also have spaces in the name, which must be adhered to. For example, Nexus Host is the actual option, and is not the same as NexusHost, nexusHost, or nexushost, all of which will cause errors.
Should there be any problems in the options file, the installer will notify you on the commandline.
Talend recommends performing a graphical or text installation first, at least to the point where the installer reports it is ready to install Talend. This ensures that, if the installer checks the database settings and finds any problems, they can be corrected before installation.
Run the installer with the --help flag to get a list of the installer options:
The view in Windows:
The view in Linux:
You can find the full list of unattended mode installer options in the Talend Help Center. These options correspond to those that are normally supplied by the installer, and can be entered on the commandline when the installer is invoked. For a complicated installation, this can become unwieldy, which is why it is possible to supply the parameters as key/value pairs in a text file—the options file.
This section explains how to create an options file using screenshots from both a graphical and a text installation. In this example the following modules are installed:
This article shows how the options file is built. The options themselves often have a set of choices and there is always a default option, which will be used if the option is not set in the options file.
The first part of an installation is to accept the license agreement. As explained earlier, this is implicit in an unattended installation.
On the next page are the general settings:
This is specified using the prefix option, as shown below:
This example uses the Advanced install style due to the level of control offered.
This is specified using the installStyle option, the two possibilities are [easy, advanced].
This example uses the Custom installation style due to the level of control offered.
This is specified using the installType option, the three possibilities are [client, server, custom].
This is specified by the licenseFile option. The file must be local to the installer.
The next page is where you specify the required components. For this example, choose the following:
Text mode installation component specifiers:
In the options file the required components are specified using the enable-components and disable-components options.
Note: For text mode installations, both options must be specified. It is not enough to use one or the other. The component specifiers must be supplied as a comma separated list.
Like the graphical installer, various components cannot be explicitly selected, for example:
They will be installed implicitly when needed, but the options to configure them will be required.
Select which Tomcat to use.
The option is tomcat and the possibilities are [install8, use]. install8 is used to install an embedded Tomcat, use will use an existing Tomcat.
These options set up the initial TAC user or the SSO connection.
For a text installation, the first option is: tacUserSelection, which specifies whether you want to set up an initial user, or set up an SSO connection (using Okta or SiteMinder). The choices are: [tacStdUser, tacSsoLabel]. For this example, specify tacStdUser.
To supply the user name and password, use the tacAdminUser and tacAdminPwd options.
The admin password must be supplied in clear text, so if this is seen to be a security hazard there are two options:
In a text installation, whether to use a Log Server is specified with tacLogServ, which is a Boolean value and therefore can be set to 0 or 1. The default is 1, that is, to set the values and send TAC messages to the Log Server. If this is 1, the other options are: tacLogServerHost and tacLogServerPort. The default values are localhost and 5044.
Select the type of database to host the TAC Administration Database.
Specify this in a text mode installation using the tacDB option with the allowed values of [H2, MySql, Oracle, MS SQL, PostgreSQL]. For this example, use a local MySQL database.
If installing an embedded Tomcat, set the port using tacPort.
Set the web application name using tacWebAppName (the default is org.talend.administrator)
Specify whether or not to install Nexus using tacInstallNexus (values are 0 or 1). The default is 1, that is, to install.
Specify whether or not to set up email notifications using tacSetupEmailNotification (values are false or true). The default is false.
This set of options will vary according to which type of database is being used as will the default values. The options are:
You can also specify the location of the database driver JAR file using tacDBDriver. If this is not set, you will need to upload the driver JAR file using the DBConfig page in the GUI once the TAC has started.
If Nexus is to be installed with a text installation, specify the configuration with the following options:
Talend recommends that you always change this value, and the best way is to reflect the environment, for example, talend-dev-central. For a text installation, the option is logservClusterName.
The associated options are:
You can specify the serv component within enable-components to set up all modules as services. It is also possible to specify individual services, should it be necessary that not all components be set up as services. The serv option must still be specified in enable-components, but there are extra options to enable the individual components to be set up as services, for example:
Once the options file is created, run the installer with the --optionfile and --unattendedmodeui parameters explicitly set to none, and the --mode parameter explicitly set to unattended.