Spring Cloud Task provides an out of the box configuration as defined in the
DefaultTaskConfigurer and SimpleTaskConfiguration. This section will walk through
the defaults as well as how to customize Spring Cloud Task for your needs
Spring Cloud Task utilizes a datasource for storing the results of task executions. By
default, we provide an in memory instance of H2 to provide a simple method of
bootstrapping development. However, in a production environment, you’ll want to configure
your own DataSource.
If your application utilizes only a single DataSource and that will serve as both your
business schema as well as the task repository, all you need to do is provide any
DataSource (via Spring Boot’s configuration conventions is the easiest way). This will
be automatically used by Spring Cloud Task for the repository.
If your application utilizes more than one DataSource, you’ll need to configure the
task repository with the appropriate DataSource. This customization can be done via an
implementation of the TaskConfigurer.
The TaskConfigurer is a strategy interface allowing for users to customize the way
components of Spring Cloud Task are configured. By default, we provide the
DefaultTaskConfigurer that provides logical defaults (Map based in memory components
useful for development if no DataSource is provided and JDBC based components if there
is a DataSource available.
The TaskConfigurer allows the configuration of three main components:
| Component | Description | Default (provided by DefaultTaskConfigurer) |
|---|---|---|
| The implementation of the |
|
| The implementation of the |
|
| A transaction manager to be used when executing updates for tasks. |
|
In most cases, the name of the task will be the application name as configured via Spring
Boot. However, there are some cases, where you may want to map the run of a task to a
different name. Spring Data Flow is an example of this (where you want the task to be run
with the name of the task definition). Because of this, we offer the ability to customize
how the task is named via the TaskNameResolver interface.
By default, Spring Cloud Task provides the SimpleTaskNameResolver which will use the
following options (in order of precedence):
spring.cloud.task.name.ApplicationContext#getId).