topic Re: Activiti with Spring Boot and two datasources in Alfresco Archive

Activiti with Spring Boot and two datasources

sebljun — Mon, 24 Aug 2015 08:54:33 GMT

I have set up a project with the Activiti Spring Boot configuration. Because I don't want to pollute the Activiti db with the tables related to the business logic of this application, I have set up two data sources:@Bean@Primary@ConfigurationProperties(prefix="datasource.app")public DataSource appDa

Re: Activiti with Spring Boot and two datasources

trademak — Wed, 26 Aug 2015 07:59:52 GMT

In the process engine configuration you can specify the datasource name. But in combination with Spring Boot I don't know the answer immediately. Did you look into the source code, how the Activiti process engine configuration is created with Activiti Spring Boot?

Best regards,

Re: Activiti with Spring Boot and two datasources

sebljun — Wed, 26 Aug 2015 09:40:10 GMT

I did now and found the configuration in DataSourceProcessEngineAutoConfiguration.

By adding this class I managed to override the default configuration and specify what data source I wanted with @Qualifier:

<java>
@Configuration
@AutoConfigureAfter(DataSourceAutoConfiguration.class)
public class ActivitiDatasourceConfiguration extends AbstractProcessEngineAutoConfiguration {
    @Bean
    public SpringProcessEngineConfiguration springProcessEngineConfiguration(
            @Qualifier("activitiDataSource") DataSource dataSource,
            PlatformTransactionManager transactionManager,
            SpringAsyncExecutor springAsyncExecutor) throws IOException {
        return this.baseSpringProcessEngineConfiguration(dataSource, transactionManager, springAsyncExecutor);
    }
}
</java>

I do not know if this is the appropriate way to do this but so far it has worked for me.

As an aside the Flyway Spring Boot integration solves this problem in a convenient way. The desired datasource is simply annotated with @FlywayDataSource. If there is interest for a similar solution, I might make an attempt at creating a pull request.