-
Open the
<classpathRoot>/alfresco-global.propertiesfile.If you have existing content in a local contentstore (i.e. where Content Services is deployed on-premises), it won't be migrated automatically but it'll still be available in the original location. New content will always be written to Azure.
-
Add the
connector.az.containerNameproperty, for example:connector.az.containerName=myazurecontainerWithin a given storage account, every container must have a unique name. If the container does not already exist, it will be created, but the name must not have already been taken. Note that two storage accounts can have containers with the same name. For more details on what a content store is, see Manage content stores.
See Naming and Referencing Containers, Blobs, and Metadata for more.
-
Add the
connector.az.deleted.containerNameproperty, for example:connector.az.deleted.containerName=myazuredeletedcontainerThis is the container that stores content once it has been deleted. For more details on what a content store is, see Manage content stores.
-
Set where the cached content is stored, and how much cache size you need.
The cached content location (and default value) is
dir.cachedcontent=${dir.root}/cachedcontent.See CachingContentStore properties for more information on the caching content store.
Note
The size of the local caching content store can be configured as necessary to limit its use to a maximum overall size or by files with a maximum file size.
For example:
# Maximum disk usage for the cache in MB system.content.caching.maxUsageMB=51200 # Maximum size of files which can be stored in the cache in MB (zero implies no limit) system.content.caching.maxFileSizeMB=0The Azure Connector supports multipart uploads where files larger than 20MB are split. The file upload is attempted and retried, in case there are issues, up to a specific limit.
-
Save the
alfresco-global.propertiesfile.You are now ready to start Content Services.