Posts Tagged ‘Upgrade’


Alfresco has recently released the Alfresco 4.0 version, and also came up with nightly build packs such as 4.0.b, 4.0.c. This informative article will be used for those users who are planning to upgrade Alfresco 3.4 to 4.0.

Alfresco has released the newer version with POSTGRESQL database, where the older versions used MYSQL database. So, in the future releases, Alfresco might go with POSTGRESQL. Instead of using the POSTGRESQL, the users still have the facility of using existing database installed in their machines such as MySql, Oracle, etc.

This upgrade procedure uses existing MYSQL database (instead of migrating the whole database to POSTGRESQL), by pointing the Alfresco installation to the MYSQL database. The upgrade from 3.4 to the higher versions like 4.0b will not work. However, applying a patch before the upgrade will help in completing the process successfully.

The following is the procedure for upgrading from 3.4 to 4.0b.

  1. Stop the Alfresco server.
  2. Keep the MySql server up and running, as we are going to use this as the database for 4.0 installation.
  3. Download ALFRESCO COMMUNITY EDITION 4.0.a, and install in the machine which has 3.4 is installed.
  4. At the time of installation, give the following details:
    driver:      org.gjt.mm.mysql.Driver
    username: alfresco
    password: root
    name:      alfresco
    url:           jdbc:mysql://localhost:3306/alfresco
  5. After the installation is complete, Copy the contentstore and contentstore.deleted folders in alf_data folder of C:\Alfresco3.4 to C:\Alfresco4.0. 
  6. Now, do the following changes in alfresco-global.properties file.
    1. Make sure that the "dir.root" location is pointing to the correct location where the alf_data is stored. For example, dir.root=C:/Alfresco4.0/alf_data.
    2. Add the following line at the end of the file, to re-index the content.
               index.recovery.mode=FULL
    3. Add the following line at the end of the file, to set the indexing system as LUCENE. (Lucene is the indexing system for versions prior to 4.0)
               index.subsystem.name=lucene
    4. Comment out the following lines
    5.                ### Solr indexing ##
                     index.subsystem.name=lucene
                     dir.keystore=${dir.root}/keystore
                     solr.port.ssl=8444
    6. Save the file.
  7. Place the MySql connector in tomcat/lib folder.
  8. Download the patch-ALF-11029-context.xml file from here, and place the file into <tomcat>/shared/classes/alfresco/extension.
  9. Start the Alfresco instance.
  10. If any errors appear, check the log file.
  11. Once the restart is done properly, and after the lucene indexes folder is created in the alf_data folder, remove the above line index.recovery.mode=FULL in alfresco-global.properties, to ensure that the indexing will not be done every time when the alfresco server is restarted.
  12. If the application is not deployed properly, and if the log file says something related indexing MPEG extension, then search for the file patch-services-context.xml, and replace the value of reindex to false for mpeg.
  13. Restart the system.

Verify whether all the data (Sites, content, etc..) is accessible through Alfresco Explorer and Share or not.

Comments are welcome. Please share your views.


It’s common for a software product to undergo changes, made by its R & D team, and to have newer versions. Basing on the changes that have implemented, the releases might be MINOR or MAJOR. The same applies for Alfresco as well. Lets discuss the upgrade process of Alfresco (Both Minor and Major upgrades).

UPGRADING TO A MINOR RELEASE:

This type of upgrade will be between the minor releases such as 3.0 to 3.0.1, 3.3 to 3.4, etc. As there will be no new features, except some small patches and minor UI changes, we can do the upgrade by simply replacing the Web Application (WAR) file.

The WAR file can be downloaded, and replaced with the existing WAR files under <install_folder>\tomcat\webapps.

The following steps can be followed for upgrading the alfresco with minor release:

1. Download the latest release of Alfresco WAR file from the Alfresco website.

2. Stop the alfresco instance. (TOMCAT and MySQL).

3. Backup the data, and the customization files.

4. Delete the Alfresco folder in <install_folder>\tomcat\webapps.

5. Replace the existing Alfresco.war file in the above said location with the recently downloaded WAR file.

6. Restore the customizations (If any).

7. Start Alfresco

The Above said procedures will upgrade Alfresco to a new minor release.

UPGRADING TO A MAJOR RELEASE:

This type of upgrade will be between the Major releases such as 2.x to 3.x, 3.x to 4.x, etc. An Alfresco’s major release contains new features, performance enhancements, and bug fixes.

The following steps can be followed for upgrading the alfresco with minor release:

1. Download the complete Alfresco package and the Tomcat bundle for the Windows operating system.

2. Stop Alfresco.

3. Backup the data, and the customization files.

4. Perform a new installation in a different folder.

5. Copy the older Alfresco file content folder to the newer installation

(Copy C:\alfresco_old_version\alf_data folder to C:\alfresco_new_version\alf_data).

6. Create a new database table, and restore the relational database content from the older database.

7. Update the Alfresco configuration file (alfresco-global.properties) in the new installation, to point to this new database.

8. Restore the customization files in the new installation.

9. Start Alfresco in the new installation.

The Above said procedures will upgrade Alfresco to a new Major release. Test thoroughly to verify whether your old configurations are working fine with the new release or not.

More information regarding the upgrade process can be found here in the alfresco site.