This section describes how to configure the Alfresco
Tuning the JVM
The hardware requirements for the Alfresco repository, Explorer 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. This section suggests metrics and estimates, but your system may vary.
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
This topic describes the 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 uses Ehcache 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 then updates the corresponding node properties with the metadata values.
Aspects are a fundamental concept related to content modeling in Alfresco. They allow the addition of 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.