The official documentation is at: http://docs.alfresco.com
This page describes the important changes for upgrading to Alfresco Community Edition 3.2.
Alfresco Community Edition 3.2 introduces the concept of subsystems. Overall defaults for subsystem properties are set in the alfresco-global.properties file.
When you upgrade to Community Edition 3.2, it is recommended that you move all your repository and database configurations from the <extension>custom-repository.properties file to the alfresco-global.properties file. For example, you should move the configuration settings for the following properties:
Sample custom content and index data location property:
Sample database connection properties:
External locations for third-party products:
Database connection properties:
Also, move any Hibernate settings from the custom-hibernate-dialect.properties file to the alfresco-global.properties file.
When you have moved your configurations, delete the custom-repository.properties file and the associated Spring context file custom-repository-context.xml, then restart the server for the settings to take effect.
Note: If you continue to use the custom-repository.properties file to set your configurations, the settings may override those set in the alfresco-global.properties file requiring more complex ongoing administration and maintenance and possibly leading to unexpected results.
Subsystems are available for the following components:
- Authentication â€“ Handles the Alfresco authentication-related functions with third-party authentication systems
- Synchronisation â€“ Performs synchronization of local user and group information with enterprise directories services such as LDAP
- IMAP â€“ IMAP Service
- File Servers â€“ CIFS, FTP, and NFS servers
- Third-Party â€“ Owns the OpenOffice, SWFtools, and ImageMagick content transformers
If you currently have configuration using any of these services we strongly recommend that you move or reconfigure these using the new alfresco-global.properties based configuration. This simplifies the setup and maintenance of these systems, and moving forwards, it will also significantly simplify any future upgrades.
For more information on configuring subsystems, see Alfresco Subsystems.
On General Upgrade Process, the general procedures include installing a new version with an entirely new data repository. Upgrading, at least from Lab 3, to CE 3.2, we can use a smoother route.
There are two components:
- The repository alf_data. We can use the current one the first time that we start up CE 3.2. Of course, with a backup copy saved elsewhere.
- The database. Include within alfresco-global.properties, only the very first time that we start up CE 3.2:
This works a lot better than trying to do a database dump and reinsert the SQLs.
One of the side-effects of the subsystem changes is that some content transformer bean declarations have been split into a declaring bean and a worker bean. If you have used the RuntimeExecutableContentTransformer for conversions before, you should change your beans as follows:
<bean id='transformer.ABC' class='org.alfresco.repo.content.transform.ProxyContentTransformer' parent='baseContentTransformer'>
<ref bean='transformer.worker.ABC' />
<bean id='transformer.worker.ABC' class='org.alfresco.repo.content.transform.RuntimeExecutableContentTransformerWorker'>
...RuntimeExec command definitions
The transformer.ABC bean controls registration and management of the mimetypes, while the transformer.worker.ABC bean is responsible for the actual transformation.