Skip to main content Skip to complementary content
Close announcements banner

Publishing a Route or Data Service Job as a Microservice to an artifact repository

Talend Studio allows you to publish your Routes and Data Service Jobs as a Microservice into an artifact repository.

Information noteNote: This feature is available only if you have installed the R2024-02 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.

Procedure

  1. Open the Route or Job that you want to build as a Microservice to an artifact repository in the design workspace.
  2. In the Deployment view of the Job tab, from the Build Type list, select Microservice. Save the Route or Job.
    Select the Microservice build type.
  3. In the Repository tree view, select the Route or Job item you want to publish into a Docker registry.
  4. Right-click it and select Publish in the menu.
  5. In the Publish wizard, select Microservice in the build type list. Click Next.
    Publish a Route as a Microservice to an artifact repository.
  6. In the options area, select:
    • The Enable Prometheus metrics endpoint check box to build the Prometheus metrics endpoint into the Microservice to monitor the execution the Job or Route, JVM memory, CPU consumption, and so on. By default, this feature bridges all the JMX attributes and values into Prometheus. For more information about Prometheus, see the Prometheus documentation. Note that for Jobs, this option works from 8.0.1-R2024-03.
    • The Export as ZIP option to export the Route to a .zip file, which provides an external config folder and start scripts to start the Microservice with the external config folder for Linux (.sh) and Windows (.bat). If this option is not selected, the Route is exported as a .jar file by default.

    Set export type and option.
  7. Click Finish to start publishing your Microservice to the artifact repository.

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!