Skip to main content Skip to complementary content
Close announcements banner

Setting up the artifact repository parameters

About this task

To retrieve all the artifacts published in the artifact repository and configure their execution, you have to connect your Talend Administration Center to the artifact repository.

For more information about how to install the artifact repository, see Installing and configuring Talend Artifact Repository.

Procedure

  1. On the Menu tree view, click Configuration.
  2. Click the Artifact Repository group to display its parameters.
    The parameters are the following:

    Parameter

    Value

    Artifact repository type

    Select the type of your artifact repository, NEXUS 3, NEXUS, or Artifactory.

    URL

    Enter the location URL of your artifact repository. For Artifactory, if the URL has no context path, then /artifactory/ will be added to the end.

    In case you do not want to use a context path, go to the configuration table of the Talend Administration Center database and set artifactory.addDefaultUrlContext parameter to false. The default context path /artifactory will not be added to the path.

    Username

    Enter the username to connect to your artifact repository.

    In case you want to enter an email address, make sure artifact.username.transform is set to true in the <tomcat_path>/WEB-INF/classes/configuration.properties file.

    Password

    Click change password and enter then confirm the password to connect to your artifact repository.

    Default Release Repo

    Enter the name of the repository into which you want to publish the Release version of your artifact items by default.

    Default Snapshot Repo

    Enter the name of the repository into which you want to publish the Snapshot version of your artifact items by default.

    Default Group ID

    Enter the name of the group in which you want to publish your artifact items by default.

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 – let us know how we can improve!