Publishing a Route or Data Service Job as a Microservice (Spring-boot) for ESB Docker image - Cloud - 7.3

Talend Studio User Guide

Version
Cloud
7.3
Language
English (United States)
Product
Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Design and Development
Available in...

Cloud API Services Platform

Cloud Data Fabric

Data Fabric

Data Services Platform

MDM Platform

Real-Time Big Data Platform

Talend Studio allows you to publish your Routes and Data Service Jobs into a Docker registry.

Procedure

  1. Open the Route or Job that you want to build as a Microservice Docker image in the design work space. In the Deployment view of the Job tab, from the Build Type list, select RouteMicroservice for Routes and Microservice for ESB for Jobs. Save the Route or Job.
  2. In the Repository tree view, select the Route or Job item you want to publish into a Docker registry.
  3. Right-click it and select Publish in the menu.
  4. In the Publish wizard, select Docker Image as the export type, and click Next.
  5. Select the Only export the default context option to export only the default context used in the Route or Job.
  6. Select the Enable Prometheus metrics endpoint check box to build the Prometheus metrics endpoint into the Microservice to monitor the execution of Routes, 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 https://prometheus.io/.
    Note:
    • This option is applicable only to Routes.
    • This option is available only if you have installed the R2020-08 Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.
  7. Select Local or specify a remote address based on your Docker engine installation.
    Warning: If you select the Remote option, make sure that Docker deamon is started with a remote port.
  8. Specify your Docker image name, and image tag.
    By default, the image name is derived from the project name and Route or Job name, and the image tag is derived from the version of the Route or Job. You can specify a new name and tag here or customize the default settings globally in Project Settings. For more information, see Customizing Docker images build settings.
    Warning: Underscore characters are not supported in Docker image names, therefore make sure the Docker image name value does not contain underscore characters.
  9. Specify your user name and password.
  10. Click Finish to start publishing your Docker image to the specified Docker registry.