Setting up multi-tenancy
Alfresco supports a single-instance, single-tenant (ST) environment where each tenant (for example, customer, company, or organization) runs a single instance that is installed on one server or across a cluster of servers.
Creating and managing workflows
Alfresco comes with a set of predefined workflow definitions which can be used right out of the box. For more complex requirements, you can also create, deploy, and manage your own Activiti workflows.
Setting up Enterprise to Cloud Sync
Enterprise to Cloud Sync gives Alfresco on-premise users the ability to synchronize their content to Alfresco in the Cloud. This feature supports scenarios where users wish to collaborate on documents with external parties that do not have access to systems behind the firewall. In these circumstances, the on-premise Alfresco instance becomes the system of record, and the cloud instance is the system of engagement for external collaboration.
When you are working with transformations, it is important to understand how file types map to one another and the transformation formats that each file type supports.
Setting up content stores
A content store provides low-level access to stored binaries ensuring that, for every write, a new binary storage location is made available. This information gives an overview on the content stores, their types, and configuration details with examples.
Setting up and managing content replication
You can automatically replicate folders and content between repositories using replication jobs. These jobs are controlled by the replication service, which finds content that needs to be replicated and then calls the transfer service to carry out the replication. Alfresco replication suits an environment where you are running multiple, separate instances of Alfresco and then replicating a subset of the content between these servers.
Importing and transferring files
Use this information to import files using the Bulk Import Tool, or transfer files using the File System Transfer Receiver (FSTR).
You can perform various migration procedures for Alfresco servers and databases.
Backing up and restoring
This information describes the process for backing up the Alfresco content repository only. It assumes that components other than the data residing in Alfresco (operating system, database, JRE, application server, Alfresco binaries and configuration, etc.) are being backed up independently.
Alfresco provides the ability to audit activity. The auditing system is disabled by default, as it has the potential to impact Alfresco ECM performance, but the auditing system is highly configurable, so that you only need generate data for those events of particular interest.