Skip to main content Skip to complementary content

Configuring the artifact repository from Talend Management Console

In Talend Management Console, you add the configuration settings for the new artifact repositories in order to share the installed libraries with all Talend Studio users automatically.

Procedure

  1. Log in to Talend Management Console.
  2. Open the Configurations page.
  3. Click Studio in the top menu.
  4. Toggle ON the Enable artifact repository configuration option.
  5. Select the type of your Artifact Repository Manager.
    • Nexus 3
    • Artifactory
  6. Enter the address of the Artifact Repository Manager.
    Default settings:
    • Nexus 3: http://localhost:8081
    • Artifactory: http://localhost:8081/artifactory
  7. In Snapshot repository ID, enter the ID of the corresponding embedded repository that you created in your artifact repository. For example, talend-custom-libs-snapshot.
  8. Similarly, enter the Release repository ID. For example, talend-custom-libs-snapshot.
  9. Enter your username and password for the Artifact Repository Manager.

    Example

    Artifact repository configuration dialog box with example values.
  10. Click SAVE.

Results

When you start the procedure to download and install missing third-party libraries from Talend Studio, and if Talend Studio is connected to Talend Management Console, it always downloads the libraries from the local repository you just set up. If a missing library doesn't exist in your local repository, it will first be downloaded from the remote repository managed by Qlik. Then this library is automatically uploaded to your local repository where Talend Studio can download it.

As a consequence, the local repository contains mostly libraries that are retrieved from the remote repository managed by Qlik. The few libraries in your local repository that are not from the remote repository are the ones that you installed manually. This happens when you need a library that is not provided by Qlik.

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!

Leave your feedback here