The following dependency has to added to your project.

The project currently provides one cluster implementation based on Infinispan.

Infinispan

<dependency>
    <groupId>org.tuxdevelop</groupId>
    <artifactId>spring-batch-lightmin-server-cluster-infinispan</artifactId>
    <version>${spring-batch-lightmin.version}</version>
</dependency>

In order to enable the server, the annotation @EnableLightminServer has to added to one of the @Configuration classes.

The Infinispan cluster configuration will provide the following clustered features:

• Synchronized poller for server scheduler and clean up jobs

• LightminServerLockManager implenentation for Infinispan

• Distributed Repositories for

  • JobExecutionEventRepository

  • JournalRepository

  • LightminApplicationRepository

If the following properties are set to true, additional distributed repositories will be provided:

1. if true, a distributed SchedulerConfigurationRepository will be provided

2. if true, a distributed SchedulerExecutionRepository will be provided

Infinispan Global Configuration

@Configuration
public class MyConfiguration {

    @Bean
    public GlobalConfiguration globalConfiguration() {
        return new GlobalConfigurationBuilder()
                // Configure the global configuration
                .build();
    }

}

The behavior of the Server Scheduler can be changed via application properties.

1. If set to false, no schedulers will be executed

2. If set to true, a new executions based on the configuration will be created on failure.

3. If set to true, a new executions based on the configuration will be created on lost after configured retries failed.

4. If true, the execution will fail if not enough instances are available.

5. Time in millis to fetch new executions to be executed by the scheduler

6. Time in millis to fetch executions to be retried by the scheduler

7. Duration of the clean up poller for the repositories

8. If set to true, the failed executions will be deleted automatically.

9. If set to true, the finished executions will be deleted automatically.

10. If set to true, the lost executions will be deleted automatically.

11. Duration how long failed executions should be kept before getting deleted automatically.

12. Duration how long finished executions should be kept before getting deleted automatically.

13. Duration how long lost executions should be kept before getting deleted automatically.

The database schema for the repositories are available in the dependency at org.tuxdevelop.spring.batch.lightmin.server.scheduler.repository

Maven Dependency

<dependency>
    <groupId>org.tuxdevelop</groupId>
    <artifactId>spring-batch-lightmin-server-scheduler-repository-jdbc</artifactId>
    <version>${spring-batch-lightmin.version}</version>
</dependency>

Enable the JDBC Repository

@EnableLightminServer
@EnableServerSchedulerJdbcRepository
@SpringBootApplication
public class MyApplication {
    ...
}

The classic client has to know where the servers are located and will send a registration request after the start up.

The dependency above will provide everything which is required for the classic client. The annotation @EnableLightminClientClassic has to added to one of the configuration classes.

The following configuration properties have to be present

1. The spring.application.name is used to identify a client and handle a cluster of the instances.

2. The url property is a list of server to which the registration request should be send.

Spring Batch Lightmin provides two implementations for the discovery client type. Both implementations add a tags to the underlying service discovery technology, so the server could identify lightmin clients.

Consul Client

<dependency>
    <groupId>org.tuxdevelop</groupId>
    <artifactId>spring-batch-lightmin-client-discovery-consul</artifactId>
    <version>${spring-batch-lightmin.version}</version>
</dependency>

@SpringBootApplication
@EnableLightminClientConsul
public class ClientApplication {

    public static void main(final String[] args) {
        SpringApplication.run(ClientApplication.class, args);
    }
}

spring:
  batch:
    lightmin:
      client:
        discovery:
          server-discovery-name: lightmin-server (1)

Eureka Client

<dependency>
    <groupId>org.tuxdevelop</groupId>
    <artifactId>spring-batch-lightmin-client-discovery-eureka</artifactId>
    <version>${spring-batch-lightmin.version}</version>
</dependency>

@SpringBootApplication
@EnableLightminClientEureka
public class ClientApplication {

    public static void main(final String[] args) {
        SpringApplication.run(ClientApplication.class, args);
    }
}

spring:
  batch:
    lightmin:
      client:
        discovery:
          server-discovery-name: lightmin-server (1)

The annotation @EnableLightminMapConfigurationRepository enables the in memory repository.

The annotation @EnableLightminJdbcConfigurationRepository enables the jdbc repository.

The jdbc repository requires a configured datasource bean with the name dataSource.

If the project configuration requires a specific datasource for the lightmin repository, the bean name can set via configuration property. More configuration options can be found in the documentation.

1. Overriding the default datasource name.

The database schema ddl and drop scripts for various databases are located in the dependency above under the path:

The annotation @EnableLightminRemoteConfigurationRepository enables the remote repository.

The remote repository can be located via url and service discovery.

For the url way, the following properties has to be set:

1. The url to the remote repository server

For the service discovery approach, the following properties has to set and a DiscoveryClient bean has to be present.

1. Enables the discovery feature

2. The discovery name of the remote repository server

Further configuration options can be found in the documentation.

For the map repository, the following configuration is enough:

For the jdbc repository, the following configuration is enough:

Properties like dataSource name, table prefix etc. can be overridden as well. Please check the documentation for more details.