Building a Route to a Spring-boot based ESB Microservice - Cloud

Talend Cloud API Services Platform Studio User Guide

English (United States)
API Services Platform
Talend Cloud
Talend Studio
Design and Development

About this task

Note: The Java methods of the context object used in the cConfig or cProcessor component, for example keySet(), entrySet(), values(), size(), are not supported in Microservice build type. These methods are supported in OSGi build type only. Because in Spring-boot the ContextProperties has to be a POJO class and it cannot extend the java.util.Properties.

To build a Route to a Spring-boot based ESB Microservice, complete the following:


  1. Click on the Studio tool bar, or select File >Edit Project Properties from the menu bar to open the Project Settings dialog box.
  2. In the tree diagram to the left of the dialog box, select Log4j to display the corresponding view.
  3. Customize the Log4j configuration as needed. The default Log4j XML instructions only output the WARN logs to the console. For more information on the log4j parameters, see
    A sample Log4j configuration is shown below which will also provide a tesb.log file when the ESB Microservice is started. Note that the Log4j configuration is the same for the Studio and the ESB Microservice. Nevertheless a log4j.xml file can also be placed into an external configuration folder of the Microservice at runtime to provide a specific Log4j configuration for production deployment.
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
    <log4j:configuration xmlns:log4j="">
        <appender name="stdout" class="org.apache.log4j.ConsoleAppender">
            <layout class="org.apache.log4j.PatternLayout">
                <param name="ConversionPattern" value="%d | %-5.5p | %-16.16t | %-32.32C %4L | %m%n"/>
        <appender name="rollingFile" class="org.apache.log4j.RollingFileAppender">
            <param name="file" value="tesb.log"/>
            <param name="MaxFileSize" value="1024KB"/>
            <param name="MaxBackupIndex" value="10"/>
            <layout class="org.apache.log4j.PatternLayout">
                <param name="ConversionPattern" value="%d | %-5.5p | %-16.16t | %-32.32C %4L | %m%n"/>
            <priority value="info"/>
            <appender-ref ref="stdout"/>
            <appender-ref ref="rollingFile"/>
  4. If the Route contains the cSOAP or cREST component, you need to use relative endpoint URL instead of absolute URL. When the Microservice is running, an embedded Tomcat container with the default 8065 port is started by Spring-boot. The REST and Soap services also run in this port. If you want to override the default port, either use the --server.port option in the command or configure it in the file in the /config folder inside the Microservice jar.
  5. Open the Route in the design work space. In the Deployment view of the Route tab, select RouteMicroservice in the Build Type list. Save the Route.
  6. In the Repository tree view, right-click the Route you want to build, and select Build Route to open the Build Route dialog box.
  7. In the To archive file field, browse to the directory where you want to save your built Route.
  8. In the Route Version area, select the version number of the Route you want to build if you have created more than one version of the Route.
  9. In the Build Type area, select ESB Microservice (Spring Boot).
  10. In the options area:
    • select the Only export the default context option to export only the default context used in the Route;

    • select 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.

    • 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
      Note: 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.
  11. Click Finish to validate your changes, complete the export operation and close the dialog box. A pop up window appears prompting you that Maven needs to be set to online to build the ESB Microservice, as some libraries have to be downloaded from the remote Maven repository. Talend Studio requires Internet access when you use the ESB Microservice feature. Talend Studio does not provide a pure offline mode for the ESB Microservice build operation. Click Yes to change Maven to online mode.
    If the Finish operation leads to an error, you can find more information in the Studio log file <Studio_Home>\workspace\.metadata\.log.


A .jar or .zip file for the Route is created in the defined place. You can run it independent of Talend Studio in standalone mode.