If you have installed the 8.0 R2022-09 Studio monthly update or a later one provided by Talend and if you are working with Talend Cloud, you can launch Talend Studio and log in to it via Talend Cloud.
Before you begin
You must have the predefined Integration Developer role to fetch the license from Talend Cloud Management Console.
- You can set the default region for Talend Cloud by adding the
-Dtalend.tmc.datacenter=<region>parameter in the corresponding .ini file under the Talend Studio installation directory according to your operating system, and
<region>is the abbreviation of the region, which can be found in the Talend Cloud URL. For example, ap for the Asia Pacific region, and us-west for the United States - West region. For more information, see Talend Cloud regions and URLs.
Go to your Talend Studio installation directory.
The Talend Studio installation directory contains binaries for several platforms including Windows, Linux, and MacOS.
you are not working on Rocky Linux 8.5, double-click the executable file
corresponding to your operating system.
Operating System Executable file
Linux on x86
MacOS on x86
MacOS on ARM
Note that if you work on MacOS and install Talend Studio manually using the zip archive file, you might get one of the following two messages as shown in below screenshots when trying to launch Talend Studio for the first time. To fix the issue, you can open the terminal, go to the directory above the Talend Studio top directory, execute the command
xattr -d com.apple.quarantine <Talend-Studio>/*, where
<Talend-Studio>is the root folder name of your Talend Studio, and then relaunch your Talend Studio.
If you are working on Rocky Linux 8.5, do the following:
Create a start.sh file under the Talend Studio installation directory and edit it by adding the following content
corresponding to the processor of your PC, where
<Talend-Studio-executable-file-name>is the Talend Studio executable file name.
#!/bin/sh export GDK_BACKEND=x11 ./<Talend-Studio-executable-file-name>
- Open the terminal.
chmod +x start.shcommand.
- Create a start.sh file under the Talend Studio installation directory and edit it by adding the following content corresponding to the processor of your PC, where
- If you launch Talend Studio for the first time, in the User License Agreement dialog box that opens, read and accept the terms of the end user license agreement.
- In the dialog box that opens, click Edit settings and in the Preferences dialog box that opens, switch to another workspace and configure the network settings if needed.
Click Log in with Talend Cloud.
You are redirected to the Talend Cloud login page.
From the Talend Cloud login page, log in to Talend Cloud either with SSO or in the regular way according to your needs, and in the
pop-up dialog box, click Open Talend_Sign_On_Tool.
For more information about logging in to Talend Cloud, see Logging in to Talend Cloud Management Console.
Switch to your Talend Studio instance.
If an Authentication dialog box for logging in to the update repositories pops up, enter your user name and password for the update repositories and click OK. For more information, see Basic authentication for update repositories in Talend Studio.
If needed, click Switch sign in to go back to where you can choose the login mode, or click and in the dialog box that opens, switch to another workspace.
- Select the branch and the project you want to work on and click Open.
You can now start working with your project and items.
If you want to use those features that are not shipped with Talend Studio by default, you need to install them using the Feature Manager wizard. For more information, see Managing features in Talend Studio.
Talend Studio requires specific third-party Java libraries or database drivers (.jar files) to be able to connect to sources and targets. These libraries or drivers, known as external modules, are required by some Talend components and/or connection wizards. Due to license restrictions, Talend may not be able to ship certain external modules within Talend Studio. For more information, see Installing external modules.