Skip to main content Skip to complementary content

Connecting Talend Studio to Talend Cloud

To allow web users in your organization to work with Artifacts you design in Studio, you must publish them to Talend Cloud. Once the connection is established, any update in your scenario from Talend Studio can be pushed to the cloud right away.

Procedure

  1. In the Studio menu bar, select Window > Preferences.
  2. From the preferences list, select Talend > Talend Cloud.
  3. Select your Authentication mode: Access token or Login name and password.
    Information noteImportant: If SSO is enabled on your Talend Cloud account, you have to use the Access token authentication mode here.
  4. Depending on the selected mode, enter the Access token or the account username and password.
    • You can generate an access token from your profile preferences in Talend Cloud.
    • If you cannot find your username or password, connect to Talend Cloud and click Forgot link/password?.

    The Talend Cloud URL is https://<env>.cloud.talend.com where <env> is the name of your Cloud region. If you do not know what your region name is, see Talend Cloud regions and URLs.

  5. Select the Advanced check box and choose your data center from the Service URL drop-down list.

    Example

    The Accelerate publish check box is selected by default for optimal performance when publishing artifacts to the cloud.

  6. Click Test Connection to test the connection to the Talend Management Console web application.
  7. Click Apply to save your settings.
  8. From the preferences list, select Talend > Performance.
  9. Adjust the Default connection timeout (seconds).
    The timeout value is set to 5 seconds by default. However, on a slower network that may not be enough. It is recommended to set the value to 300 seconds.
  10. Click Apply to save your settings and close the Preferences window.
    The connection has been established and you are now able to publish Artifact to Talend Management Console.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!