StepExecutionListener - Adding hooks or listeners - Spring Batch Part 8

By -
You can add interceptors to you steps by using the Listeners around your steps. We will check the StepExecutionListener - no points for guessing what it does - in this blogpost.

We add add listeners both before and after Steps.

Lets consider that along with Corporate Gifts, you also want to supply beautifully arrange chocolates. Lets create a job for it.


@Bean
public Job orderChocolateBoxJob(){
   return this.jobBuilderFactory.get("orderChocolateBoxJob")
         .start(selectChocolatesStep())
         .next(arrangeChocolatesStep())
         .build();
}

@Bean
public Step selectChocolatesStep(){
   return this.stepBuilderFactory.get("selectChocolatesStep").tasklet(new Tasklet() {
      @Override
      public RepeatStatus execute(StepContribution contribution, ChunkContext chunkContext) throws Exception {
         System.out.println("Ordering Chocolate : "+ chunkContext.getStepContext().getJobParameters().get("chocolateType").toString());
         return RepeatStatus.FINISHED;
      }
   }).build();
}

@Bean
public Step arrangeChocolatesStep(){
   return this.stepBuilderFactory.get("arrangeChocolatesStep").tasklet(new Tasklet() {
      @Override
      public RepeatStatus execute(StepContribution contribution, ChunkContext chunkContext) throws Exception {
         System.out.println("Ordering Chocolate : "+ chunkContext.getStepContext().getJobParameters().get("chocolateType").toString());
         return RepeatStatus.FINISHED;
      }
   }).build();
}
Our orderChocolateBox consists of two steps:
  1. Selecting the Chocolates
  2. Arranging the Chocolates 
The Client may order Almond Chocolates or Plain Chocolates. Whenever the Client orders Almond Chocolates, we want to add a not which says " Chocolate box contains nuts"

Lets see how we can do that using StepExecutionListener.
This listener should be added after we select the chocolates from the selectChocolatesStep. As you can see, we are passing chocolateType program parameter from our runConfiguration:

"chocolateType=Almonds"

Lets create the Listener:
package com.ricsr.springbootdemo;

import org.springframework.batch.core.ExitStatus;
import org.springframework.batch.core.StepExecution;
import org.springframework.batch.core.StepExecutionListener;

public class ChocolateTypeStepExecutionListener implements StepExecutionListener {
    @Override
    public void beforeStep(StepExecution stepExecution) {
        System.out.println("Before arranging chocolates");
    }

    @Override
    public ExitStatus afterStep(StepExecution stepExecution) {
        System.out.println("After arranging chocolates");
        String chocolateType = stepExecution.getJobParameters().getString("chocolateType");
        return chocolateType.equals("Almonds") ? new ExitStatus("NUTTY_CHOCOLATES") : new ExitStatus("NORMAL_CHOCOLATES");
    }
}
As you can see, the StepExecutionListener has two methods:
  1. beforeStep: Executes before the step executes. Lets add a sysout statement here.
  2. afterStep: This will execute after the step executes. In our case, this is where we add the logic to determine if the chocolate contains NUTS or not, and which will drive whether we add a note to our chocolate box or not. We are making use of custom ExitStatus for the same. Obviously, we can have more categories of chocolate types, but lets leave it simple for the sake of our example. 
Lets go back to our SpringbootdemoApplication class. And add a bean for the listener:
@Bean
public StepExecutionListener chocolateTypeStepExecutionListener(){
   return new ChocolateTypeStepExecutionListener();
}

Lets add the listener to our selectChocolatesStep We use the listener method on the builder to add our listener:
@Bean
public Step selectChocolatesStep(){
   return this.stepBuilderFactory.get("selectChocolatesStep").tasklet(new Tasklet() {
      @Override
      public RepeatStatus execute(StepContribution contribution, ChunkContext chunkContext) throws Exception {
         System.out.println("Ordering Chocolate : "+ chunkContext.getStepContext().getJobParameters().get("chocolateType").toString());
         return RepeatStatus.FINISHED;
      }
   }).listener(chocolateTypeStepExecutionListener()).build();
}

Let us run with Program parameter: "chocolateType=NUTTY"

2020-07-21 23:12:36.801  INFO 17884 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [FlowJob: [name=orderChocolateBoxJob]] launched with the following parameters: [{chocolateType=Almonds}]
2020-07-21 23:12:36.821  INFO 17884 --- [           main] o.s.batch.core.job.SimpleStepHandler     : Executing step: [selectChocolatesStep]
Before arranging chocolates
Ordering Chocolate : Almonds
After arranging chocolates
2020-07-21 23:12:36.837  INFO 17884 --- [           main] o.s.batch.core.step.AbstractStep         : Step: [selectChocolatesStep] executed in 16ms
2020-07-21 23:12:36.860  INFO 17884 --- [           main] o.s.batch.core.job.SimpleStepHandler     : Executing step: [addNoteStep]
Chocolate box contains nuts
2020-07-21 23:12:36.879  INFO 17884 --- [           main] o.s.batch.core.step.AbstractStep         : Step: [addNoteStep] executed in 19ms
2020-07-21 23:12:36.904  INFO 17884 --- [           main] o.s.batch.core.job.SimpleStepHandler     : Executing step: [arrangeChocolatesStep]
Ordering Chocolate : Almonds
2020-07-21 23:12:36.921  INFO 17884 --- [           main] o.s.batch.core.step.AbstractStep         : Step: [arrangeChocolatesStep] executed in 16ms
2020-07-21 23:12:36.935  INFO 17884 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [FlowJob: [name=orderChocolateBoxJob]] completed with the following parameters: [{chocolateType=Almonds}] and the following status: [COMPLETED] in 124ms
2020-07-21 23:12:36.939  INFO 17884 --- [extShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown initiated...
2020-07-21 23:12:36.957  INFO 17884 --- [extShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown completed.

BUILD SUCCESSFUL in 5s


Now, let us run with Program parameter: "chocolateType=DARK"

2020-07-21 23:13:40.962  INFO 2284 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [FlowJob: [name=orderChocolateBoxJob]] launched with the following parameters: [{chocolateType=DARK}]
2020-07-21 23:13:40.986  INFO 2284 --- [           main] o.s.batch.core.job.SimpleStepHandler     : Executing step: [selectChocolatesStep]
Before arranging chocolates
Ordering Chocolate : DARK
After arranging chocolates
2020-07-21 23:13:40.998  INFO 2284 --- [           main] o.s.batch.core.step.AbstractStep         : Step: [selectChocolatesStep] executed in 12ms
2020-07-21 23:13:41.019  INFO 2284 --- [           main] o.s.batch.core.job.SimpleStepHandler     : Executing step: [arrangeChocolatesStep]
Ordering Chocolate : DARK
2020-07-21 23:13:41.029  INFO 2284 --- [           main] o.s.batch.core.step.AbstractStep         : Step: [arrangeChocolatesStep] executed in 10ms
2020-07-21 23:13:41.036  INFO 2284 --- [           main] o.s.b.c.l.support.SimpleJobLauncher      : Job: [FlowJob: [name=orderChocolateBoxJob]] completed with the following parameters: [{chocolateType=DARK}] and the following status: [COMPLETED] in 72ms
2020-07-21 23:13:41.040  INFO 2284 --- [extShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown initiated...
2020-07-21 23:13:41.052  INFO 2284 --- [extShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown completed.

BUILD SUCCESSFUL in 3s


Note: I have dropped the Spring Job Repository tables just to able to rerun the application just to make it easy to rerun the Job

DROP TABLE BATCH_STEP_EXECUTION_CONTEXT ;
DROP TABLE BATCH_STEP_EXECUTION ;
DROP TABLE BATCH_JOB_INSTANCE ;
DROP TABLE BATCH_JOB_EXECUTION_PARAMS ;
DROP TABLE BATCH_JOB_EXECUTION_CONTEXT ;
DROP TABLE BATCH_JOB_EXECUTION ;

Comments

Post a Comment

Popular posts from this blog

Writing your own ejabberd Module

By -
Coming soon: What is ejabberd? What is erlang? Installation details. I will start with writing the ejabberd module first. Once you have done all the installations: sudo make sudo make install sudo ejabberdctl start sudo ejabberdctl stop You can check the status using: sudo ejabberdctl status You can locate logs at: (With default installation) /var/log/ejabberd All config related changes will be mainly done at: /etc/ejabberd/ejabberd.yml You will need a basic understanding of erlang. You can take a short crash course at: http://www.erlang.org/course/course.html This is a good reference. Go to your ejabberd-15.07/src directory. This is where you will write the hook for your ejabberd server. Create a file, say mod_changeBody.erl. Your module name and file name should be same. Add the following basic contents into your erl file: -module(mod_changeBody). -behavior(gen_mod). -include("ejabberd.hrl"). -include("logger.hrl"). -expo
Read more

npm ECONNREFUSED error

By -
If you face error which says ECONNREFUSED while doing npm install <<package name>>, you are probably behind a proxy which is not allowing you to connect to the server and download the packages required. Just follow the below steps: npm config set proxy  http://your_proxy_name:port npm config set https-proxy https://your_proxy_name:port And then try npm install How to get npm config? npm get proxy will do the work :)
Read more

Conditional Flow - Spring Batch Part 6

By -
Jump to Conditional Flow using Custom Status There can be muliple scenario where you want your jobs to proceed depending on the outcome of your steps. For example, in case of our Corporate gifts shop, in case the automatic packaging of the gifts fails, we want some manual intervention to be done i.e. somebody should manually package the item.  IF-ELSE IF loop for packaging:     if packageStep fails                              then manualPackageStep                         else if packageStep executes successfully                              then sendOutForDelivery Entire code available at git repo:   https://github.com/ricsr/spring-batch-demo/tree/exercise_06 Using SpringBatch you can achieve it as follows: Create you manualPackageStep, which is very similar to your packageStep, except that it does the packaging manually. @Bean public Step manualPackageStep () { return this . stepBuilderFactory .get( "manualPackageStep" ).tasklet( new Tasklet() { @Override pu
Read more