Skip to main content Skip to complementary content

Setting up update repositories by hosting them

You can set up the update repositories, also called p2 repositories, by hosting the official Talend repositories. This setup is recommended for centralizing the updates and making them available to Talend Studio users who don't have access to the internet.

About this task

This procedure shows you how to set up the update repositories for Talend Studio feature packages and a Talend Studio monthly update using Apache Tomcat by hosting the official Talend repositories.

Procedure

  1. Download the archive for Talend Studio feature packages from the official Talend repository, Talend_Full_Studio_p2_repository-YYYYMMDD_HHmm-VA.B.C.zip in this example.
  2. Extract the archive for Talend Studio feature packages in the webapps folder of Apache Tomcat.
  3. Rename the folder for Talend Studio feature packages to repo-base, for example.
  4. Download the archive for the Talend Studio monthly update from the official Talend repository, for example, Patch_20220923_R2022-09_v1-8.0.1.zip for 8.0 R2022-09 Talend Studio monthly update.
  5. Extract the archive for the Talend Studio monthly update in the webapps folder of Apache Tomcat.
  6. Rename the folder for the Talend Studio monthly update to repo-update, for example.
  7. Start Apache Tomcat.
    Later, you can use http://<repo-server>/repo-base and http://<repo-server>/repo-update to configure the base URL and the update URL in Talend Studio or the -Dtalend.studio.p2.base and -Dtalend.studio.p2.update parameters in Continuous Integration, where <repo-server> is the IP address or the host name of the Apache Tomcat server.

    Note that you can also use other server tools besides Apache Tomcat, and you can even host a repository using a local folder and then configure the URL using the complete path to the folder.

What to do next

Configure the base and update URLs in Talend Studio or in Continuous Integration.

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