Tuning the JVM
The hardware requirements for the Alfresco repository and Share are variable and depend on the number of concurrent users that access the system. You can tune the memory and garbage collection parameters for the JVM to be appropriate for your situation.
Command line configuration
The beans that load the alfresco-global.properties will give preferential treatment to any JVM-set properties.
Configuring Alfresco to work with a web proxy
There are standard JVM system properties that you can use to set proxies for various protocol handlers, such as HTTP and HTTPS. These properties are used by Surf and all other parts of the system that make http call-outs.
Configuring the repository cache
The Alfresco repository provides in-memory caches. These caches are transaction safe and can be clustered. Caches greatly improve repository performance but they use Java heap memory.
Configuring metadata extraction
Metadata extraction automatically extracts metadata information from inbound and/or updated content and updates the corresponding nodes properties with the metadata values.
Aspects allow you to add functionality to existing content types.
Versioning allows you to track content history. By default, content that is created in the repository is not versionable. When creating content, users must specify versionable on a case-by-case basis.
You can use the cm:indexControl aspect to control the indexing of content in Alfresco Share. Using this aspect you can choose to disable repository-wide indexing. This can prove useful in certain situations, such as bulk loading.
Deferring the start of cron based jobs
You can configure alfresco-global.properties and dev-log4j.properties to implement a global delay to cron based jobs; for example, until after the server has fully started.