Skip to main content Skip to complementary content
Announcements

Building a Job as a Microservice (Spring-boot) for ESB Docker image

About this task

In the Build Job dialog box, you can build a Data Service Job as a Microservice (Spring-boot) for ESB Docker image in order to execute it on a Docker engine.
Information noteWarning: Only Jobs that include the tRESTRequest component can be built as a Spring-boot based ESB Microservice Docker image.

Procedure

  1. Open the Job that you want to build as a Microservice in the design work space. In the Deployment view of the Job tab, select Microservice for ESB from the Build Type list. Save the Job.
  2. In the Repository tree view, right-click the Job you want to build, and select Build Job to open the Build Job dialog box.
  3. In the Job Version area, select the Data Service Job you want to build if you have created more than one version of the Job.
  4. In the Build type area, select Microservice (Spring-boot) for ESB Docker image to build your Job as a Microservice Docker image.
  5. Select the Only export the default context option to export only the default context used in the Job.
  6. Select Local or specify a remote address based on your Docker engine installation.
    Information noteWarning: If you select the Remote option, make sure that Docker deamon is started with a remote port.
  7. Specify your Docker image name, and image tag.
    By default, the image name is derived from the project name and Job name, and the image tag is derived from the version of the 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.
    Information noteWarning: Underscore characters are not supported in Docker image names, therefore make sure the Docker image name value does not contain underscore characters.
  8. Click Finish to build your Microservice Docker image.

Results

You Job is build as a Microservice (Spring-boot) for ESB Docker image and ready to run on your Docker engine.

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!

Leave your feedback here