To implement MT, the Alfresco ECM has been logically partitioned such that each tenant has access to their own set of tenant-specific stores. These stores are typically routed to their own physical root directory. Also, if using Lucene (Alfresco 3.4.x or Alfresco 4.0.x configured for ‘lucene’ search subsystem) then the Lucene index files are partitioned, since Alfresco maintains a Lucene index per store.
All ECM-related services are partitioned including node services, security services, workflow services, search/index services, dictionary services etc. Also, in order to support MT Alfresco Share, additional partitioned services include site services, activity services, invite services, avm services etc.
The meta-data is logically partitioned within the DB schema.
Clustering
The MT features have been designed and implemented to work in a clustered configuration.
Cache size
If you wish to support a large number of tenants (eg. > 99) then you will need to review and increase the cache size for all of the tenant caches, that are by default configured to 100 (including the default domain). Please refer to:
- cache-context.xml
- ehcache-custom-cluster.xml.sample.cluster
Tenant-based caches currently include:
- webScriptsRegistryCache (RepositoryContainer)
- prefixesCache (NamespaceDAOImpl)
- compiledModelsCache (DictionaryDAOImpl)
- messagesCache (MessageServiceImpl)
- loadedResourceBundlesCache (MessageServiceImpl)
- resourceBundleBaseNamesCache (MessageServiceImpl)
Modules
Alfresco supports the ability to pre-package AMPs (Alfresco Module Packages) into the Alfresco WAR which will be installed into the default domain on startup. In a multi-tenant environment, the module will also be installed into each tenant domain when the tenant is created or imported.
Note: As of Alfresco 4.2d, the functionality of a AMP may still apply to tenants depending on the implementation, but ModuleComponents will not be installed into each tenant domain. See ALF-19207
