[ 
https://issues.apache.org/jira/browse/FINERACT-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Norbert Táskai updated FINERACT-1667:
-------------------------------------
    Description: 
In the context of this story we have to integrate Spring Batch into Fineract 
and utilizing it for starting the existing batch jobs. The most convenient 
plain and simple solution is to simply turn the existing jobs into tasklets, at 
least for this story. This way the batch jobs will function as they should with 
no impact on the business logic.

*Acceptance criteria:*
 * Spring Batch is integrated into Fineract

 * The existing batch jobs are started as Spring Batch jobs

 * Liquibase creates the necessary table structure for Spring Batch upon startup

*Note:*
 * The existing batch jobs can be identified by search for the @CronTarget 
annotation in the code.

 * The PostgreSQL database structure is shipped with the Spring Batch package 
under {{org.springframework.batch.core}} named {{schema-postgresql.sql}}

 * The MySQL database structure is shipped with the Spring Batch package under 
{{org.springframework.batch.core}} named {{schema-mysql.sql}}

> Integrate Spring Batch into existing jobs as Tasklets
> -----------------------------------------------------
>
>                 Key: FINERACT-1667
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1667
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Norbert Táskai
>            Priority: Major
>
> In the context of this story we have to integrate Spring Batch into Fineract 
> and utilizing it for starting the existing batch jobs. The most convenient 
> plain and simple solution is to simply turn the existing jobs into tasklets, 
> at least for this story. This way the batch jobs will function as they should 
> with no impact on the business logic.
> *Acceptance criteria:*
>  * Spring Batch is integrated into Fineract
>  * The existing batch jobs are started as Spring Batch jobs
>  * Liquibase creates the necessary table structure for Spring Batch upon 
> startup
> *Note:*
>  * The existing batch jobs can be identified by search for the @CronTarget 
> annotation in the code.
>  * The PostgreSQL database structure is shipped with the Spring Batch package 
> under {{org.springframework.batch.core}} named {{schema-postgresql.sql}}
>  * The MySQL database structure is shipped with the Spring Batch package 
> under {{org.springframework.batch.core}} named {{schema-mysql.sql}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to