Talend Artifact Repository
The artifact repository delivered by Qlik and based on Sonatype Nexus is a preconfigured application centralizing the management and usage of the Software Update, User libraries and snapshots and releases repositories:
-
Software Update is used to manage application updates (patches) distributed by Qlik. By default the talend-updates repository is embedded within Software Update and retrieves the updates published by Qlik. This repository allows the user to visualize the updates available.
-
The User libraries repository is used to store all external libraries. These libraries are retrieved by Talend Studio at start-up and shared with Talend Administration Center using the talend-custom-libs repository.
-
The snapshots and releases repositories are used as a catalog in which all artifacts to be deployed and executed are stored. These artifacts are designed by the user from Talend Studio or any other Java IDE. By default, the snapshots repository is used for development purposes and the releases repository is used for production. These repositories make artifacts available for deployment and or execution in an execution server.
Qlik also support JFrog Artifactory to be used with Talend server modules. An archive containing Talend scripts to initialize the Artifact repository is delivered in the Talend Administration Center package.
Software update repository
The following image shows the architecture of Software Update linked to Talend Administration Center and to the Talend Studio.
To download and install some software updates, you need to connect to Software Update (integrated within the Talend Artifact Repository) and its embedded repository named talend-updates.
To do so, you must install Talend Artifact Repository on your machine and log in its Web interface.
In Talend Administration Center, the patches available for the current version that have been copied from the Talend remote repository to the local talend-updates repository are detected and the administrator can accept them.
Talend Studio is connected to Talend Administration Center to retrieve the repository connection information and the updates are detected and installed automatically.
For more information on how to check updates using these repositories, see the Talend Administration Center and Talend Studio User Guides.
User Libraries repository
The following image shows the architecture of the User Libraries repository.
To download and install some specific third-party Java libraries or database drivers that are needed by Talend Studio, you need to connect to the User Libraries repository (integrated within the Talend Artifact Repository) and its embedded repository named talend-custom-libs-release.
To do so, you must install Talend Artifact Repository on your machine and log in its Web interface.
When Talend Studio opens, the external libraries missing from the local talend-custom-libs-release repository are detected. You are prompted to download them from the remote artifact repository, hosted by Qlik, and install them.
Talend Administration Center is connected to Talend Studio and to the local repository and the installed libraries are shared automatically.
Snapshots and Releases artifact repositories
The following image shows the architecture of the snapshots and releases repositories linked to Talend Studio, to an execution server and to Talend Administration Center.
The artifact repository is also used to store as artifacts all the Services, Routes, and Jobs created in Talend Studio or any Generic OSGi Feature created in any other Java IDE.
From Talend Studio, you can publish those artifacts in the snapshots and releases repositories (integrated in Talend Artifact Repository). The artifacts are provided to an execution server and then can be selected through Talend Administration Center in order to set their deployment.
Talend Administration Center also fetches the artifact status and URLs and display them in its page Job Conductor and, if available, ESB Conductor.
When the deployment of an artifact is initiated in Talend Administration Center, the execution server requests the corresponding artifact in the artifact repository. Then, the artifact can be deployed and executed.
- a snapshots repository to publish snapshot artifacts for development purposes
- a releases repository to publish stable artifacts for production purposes