Class MultiSchemaMultiTenantProcessEngineConfiguration

java.lang.Object
org.activiti.engine.ProcessEngineConfiguration
org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl
org.activiti.engine.impl.cfg.multitenant.MultiSchemaMultiTenantProcessEngineConfiguration

@Deprecated public class MultiSchemaMultiTenantProcessEngineConfiguration extends ProcessEngineConfigurationImpl
Deprecated.
multi-tenant code will be removed in future version of Activiti and Activiti Cloud
A ProcessEngineConfiguration that builds a multi tenant ProcessEngine where each tenant has its own database schema. If multitenancy is needed and no data isolation is needed: the default ProcessEngineConfigurationImpl of Activiti is multitenant enabled out of the box by setting a tenant identifier on a DeploymentBuilder. This configuration has following characteristics: - It needs a TenantInfoHolder to determine which tenant is currently 'active'. Ie for which tenant a certain API call is executed. - The StrongUuidGenerator is used by default. The 'regular' DbIdGenerator cannot be used with this config. - Adding tenants (also after boot!) is done using the registerTenant(String, DataSource) operations. - Currently, this config does not work with the 'old'
invalid reference
JobExecutor
, but only with the newer AsyncExecutor. There are two different implementations: - The ExecutorPerTenantAsyncExecutor: creates one full AsyncExecutor for each tenant. - The SharedExecutorServiceAsyncExecutor: created acquisition threads for each tenant, but the job execution is done using a process engine shared ExecutorService. The AsyncExecutor needs to be injected using the ProcessEngineConfiguration.setAsyncExecutor(AsyncExecutor) method on this class. databasetype