User interface and installation modes of Talend Installer

Talend MDM Platform Installation Guide

EnrichVersion
6.1
EnrichProdName
Talend MDM Platform
task
Installation and Upgrade
EnrichPlatform
Talend Identity Management
Talend Administration Center
Talend Artifact Repository
Talend Activity Monitoring Console
Talend MDM Server
Talend Project Audit
Talend Studio
Talend ESB
Talend SAP RFC Server
Talend DQ Portal
Talend JobServer
Talend CommandLine
Talend Log Server
Talend Installer
Talend Repository Manager
Talend Runtime
Talend MDM Web UI

This section provides information about the different installation modes that Talend Installer can run in.

Note that the log files generated during the installation can be found in C:\Users\<username>\AppData\Local\Temp on Windows, and in /tmp/ on Linux.

Note also that, once Talend Installer has completed the installation of the products, a directory (called Talend by default) is created with sub-folders for each Talend product.

Installation modes

Three main installation modes are available:

  • The Full Graphic mode: allows full interactivity through a graphical user interface.

  • The Text mode: provides full interactivity with users in the command line. It is equivalent to any GUI mode but the pages are displayed in text mode in a console.

    The image below shows an example of text mode where the user enters the --mode text option from the command line on a OS X system:

    Note

    This installation mode is only available on Unix platforms. It is automatically used if no graphical mode is available but it also can be forced using the --mode text command.

  • The Unattended mode: is especially useful for automating the installation processes. This silent mode will perform an unattended installation that will not prompt the user for any information.

To perform this Unattended installation:

  1. Write a simple .txt script in which you will define the options values. For a complete list of values, use the help command or see Talend Installer Unattended mode available options.

    In this example, the script details the silent installation of the Server type (full type). The installation directory that will be created is called Install and the license file used is located in the C:/licenses directory.

    You can also create a script for a Custom type installation for example: in this case, specify in your script the products and modules to install as well as the configuration information of these products. For example, the enable-components parameter allows you to do a comma-separated list of these products, while the tacPort parameter allows you to specify the port to use for Talend Administration Center. For more information about the available parameters and their values, enter help in the console.

  2. Launch the silent installation using the --optionfile <filename> command, where <filename> is the name of the script which contains the list of pairs <key>=<value>.

    An unattended installation is performed.

Note

If you want to install Talend products as services via the Installer and you are on Windows Vista or Windows 7, you are required to run the application as Administrator OR to disable User Account Control.

For more information on these installation modes, please refer to the online Bitrock documentation.

Installation types and styles

Three installation types are available:

  • The Server type: allows you to install all Talend server components with default configuration.

  • The Client type: allows you to install the Talend Studio.

  • The Custom type: allows you to select and configure the Talend solutions that will be installed.

By default, the Easy install option is selected and will install the Talend solutions with default configuration (default local host, default ports and so on) without asking you for any information. Before performing this installation, make sure the default ports are not used by other applications. For more information, see Port information.

To customize the installation of your solutions, select the Advanced Install option (combined with a Custom type installation for example).

If you are on Linux, you might need to add the hostname information regarding the CommandLine in <install_folder>/cmdline/stop_cmdline.sh. Make sure the java commands contain the hostname information like in the following example:

java -jar ../utils/telnet.jar localhost 8002 initLocal
java -jar ../utils/telnet.jar localhost 8002 stopServer