You need now to define on which server(s) you will install Talend Runtime.
First select the servers that will be used for the execution.
Then, on each server, unzip the archive file containing the Talend Runtime application matching your release version of Talend.
The archive file name for example reads: Talend-Runtime-V5.0.0.zip
In the unzipped file you might need to configure the files org.ops4j.pax.web.cfg to change the HTTP listening port and org.apache.karaf.management.cfg to manage RMI connection to connect to Talend ESB Container via JMX, that you can find in the directory Talend-Runtime-VA.B.C/etc. Note that this file also allows you to define the artifact repository URL.
To launch Talend Runtime, browse to the bin directory and run the trun.bat file on Windows and the trun file on Linux.
Now we simply have to declare these runtime instances in the Web application and their resources (CPU, RAM, etc.) should become available. To do this:
Go to the Servers page of Talend Administration Center.
Only users that have Operation Manager role and rights can have a read-write access to this page. For more information on access rights, see your Talend Administration Center User Guide. So, you have to connect to Talend Administration Center as an Operation Manager to be able to configure your servers.
And define the server as follows:
Type in the description of server.
File transfer port
Timeout on unknown status(s)
Type in the username for user authentication to access a Job server.
Type in the password for user authentication to access a Job server.
Select/clear the check box to activate/deactivate this server
Select/clear the check box to use or not your own SSL Keystore to encrypt the data prior to transmission.
For more information about how to enable SSL, see Enabling the SSL encryption.
By default, servers created are Job servers.
To deploy and execute your Jobs, Services, Routes or Generic tasks into Talend Runtime, select the Talend Runtime check box. The following fields will display: Mgmt-Server port, Mgmt-Reg port, Admin Console port and Instance.
Mgmt-Server port RMI Server Port (44444 by default). This field is mandatory. Mgmt-Reg port RMI Registry Port (1099 by default). This field is mandatory. Admin Console port Port of the Administration Web Console (8040 by default). This field is mandatory and allows to activate the Admin server button allowing you to access the Administration Web console. Instance Type in the name of the container instance in which you will deploy and execute your Jobs, Services, Routes or Generic tasks, trun by default.
This corresponds to the configuration of a Talend Runtime on the system that hosts the Web application. For any other system, the Host field should contain the IP address of the system. Check also that the ports 8000, 8001 and 8888 are available. These ports must be the same as defined in the TalendJobServer.properties defined above. Note that if no username and password pairs are defined in the file users.csv in the directory <root>/conf/ where <root> is the JobServer path, then you do not have to set the Username and the Password.
Click the Servers page again so that the Talend Runtime servers appear with their properties.