Skip to content
master
Go to file
Code
This branch is 78 commits ahead of pschalk:master.

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.adoc

camunda-bpm-custom-batch

camunda bpm custom batch
License Apache%202.0 blue
badge

The goal of this camunda extension is to provide an simple way of using the camunda batch functionality. Camunda Batch could be used to split a huge workload into small asynchronous jobs. With this extension, we want to open the camunda batch functionality to everyone.

Why should I use this extension

Camunda batch is really cool for offloading huge workload into small asynchronous pieces of work. E.g.:

  • Unclaiming / Updating a huge list of camunda tasks

  • Call APIs with batches of data

  • Distribution of emails

  • Technical stuff like clean-up

Get started

The extension will be published on maven central, so if you are using maven, just add the dependency:

Maven Users:

<dependency>
  <groupId>org.camunda.bpm.extension.batch</groupId>
  <artifactId>camunda-bpm-custom-batch-core</artifactId>
  <version>1.5.0</version>
</dependency>

Gradle Users:

compile("org.camunda.bpm.extension.batch:camunda-bpm-custom-batch-core:1.5.0")

First you have to define an own job handler for working on the single batch data:

@Component
public class PrintStringBatchJobHandler extends CustomBatchJobHandler<String> {
  @Override
  public void execute(List<String> data, CommandContext commandContext) {
      logger.info("Work on data: {}", data.get(0));
  }

  @Override
  public String getType() {
      return "print-string-batch-handler";
  }
}

Next you have to notify the engine about this job handler, e.g. with spring-boot:

@Bean
public ProcessEnginePlugin customBatchHandlerPlugin(PrintStringBatchJobHandler printStringBatchJobHandler) {
  return CustomBatchHandlerPlugin.of(printStringBatchJobHandler);
}

Finally, the creation of the batch itself:

CustomBatchBuilder.of(listOfStringData)
  .jobHandler(printStringBatchJobHandler)
  .create();

Or with more configuration:

CustomBatchBuilder.of(listOfStringData)
  .configuration(engineConfiguration)
  .jobHandler(printStringBatchJobHandler)
  .jobsPerSeed(10)
  .jobPriority(0L)
  .invocationsPerBatchJob(5)
  .exclusive(true)
  .create(engineConfiguration.getCommandExecutorTxRequired());

Note: The batch jobPriority is only considered when using Job Executor with the corresponding Acquisition Strategy jobExecutorAcquireByPriority. (see camunda documentation) The seed and monitor jobs receive the same priority as the batch.

Versions

1.5

  • BREAKING CHANGES: This version is needed to be compatible with Camunda Version 7.13! (It will NOT work with with lower camunda versions)

1.4

  • Use gson as json converter to be compatible with camunda release 7.11

1.3

  • Batch Configuration gets now saved as json, but it’s still possible to work on "old" batches because the extension is downwards compatible

  • It’s now possible to set exclusive flag for batch jobs (see Camunda Job Docs)

1.2

  • Batch Job priority could be set

Roadmap

todo

  • Provide a data collector class

  • Provide a timer job for automatically triggering of batch creation

Resources

Maintainer

Contributors

Sponsor

License

Apache License, Version 2.0

About

using the camunda batch execution for custom batch runs

Topics

Resources

License

Languages

You can’t perform that action at this time.