Our way from Alfresco 4.2.c to Alfresco 5.0.c

Alfresco CE 5.0.c release, the first in this branch ready to use in productive environments, allowed us to upgrade our document management server. Following, some notes on our upgrading process are included.

Scenario

  • Alfresco 4.2.c available running on PostgreSQL 9.1 over Ubuntu 14
  • 15 Gb of storage and 60,000 documents
  • LDAP authentication integrated against OpenLDAP
  • Different AMPs modules for customizations
  • Custom backup process

Planning

In order to get a successful upgrading, we reviewed Alfresco upgrading workflow:

  • Validate requirements
  • Backup Alfresco 4.2.c (filesystem, optionally Solr indexes and database)
  • Install Alfresco 5.0.c in a new path
  • Validate Alfresco 5.0.c installation
  • Apply previous configuration and deploy AMP modules
  • Restore backup from 4.2.c on new Alfresco 5.0.c installation
alfresco singleupgrade

Stages for upgrading Alfresco (from docs.alfresco.com)

Executing

Note. This steps are only an example, your system may require any other operations.

# Stop Alfresco
$ service alfresco stop

# Backup Alfresco 4.2.c (filesystem and database)
$ mv alfresco alfresco-old
$ pg_dump alfresco > alfresco-4.2.c.sql

# We omitted Solr indexes backup at this point

# Install Alfresco 5.0.c
$ wget http://dl.alfresco.com/release/community/5.0.c-build-00145/alfresco-community-5.0.c-installer-linux-x64.bin
$ chmod +x alfresco-community-5.0.c-installer-linux-x64.bin
$ ./alfresco-community-5.0.c-installer-linux-x64.bin
Launch Alfresco Community Share [Y/n]: Y

# Apply previous configuration (LDAP, alfresco-global.properties, AMPs...)
$ service alfresco stop
$ mkdir -p /opt/alfresco/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap-ad/ldap-ad1
$ cp /opt/alfresco-old/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap-ad/ldap-ad1/*
\ /opt/alfresco/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap-ad/ldap-ad1
$ ...

# Restore backup from Alfresco 4.2.c
$ rm -rf /opt/alfresco/alf_data/contentstore
$ rm -rf /opt/alfresco/alf_data/contentstore.deleted
$ cp -r /opt/alfresco-old/alf_data/contentstore /opt/alfresco/alf_data
$ cp -r /opt/alfresco-old/alf_data/contentstore.deleted /opt/alfresco/alf_data

$ psql
# drop database alfresco;
# CREATE DATABASE alfresco
# WITH OWNER = alfresco
# ENCODING = 'UTF8'
# TABLESPACE = pg_default
# CONNECTION LIMIT = -1
# TEMPLATE template0;

$ psql alfresco < alfresco-4.2.c.sql

# Rebuild from scratch Solr indexes
$ rm -rf /opt/alfresco/alf_data/solr4/*/*

# Start Alfresco 5.0.c
$ service alfresco start

As Richard Esplin noted at keensoft blog entry, Solr indexes can be backed up and restored. If so, searches are available at boot time and users have no wait on starting to use the system with full capabilities.

Spanish blog source at keensoft

Responder

Introduce tus datos o haz clic en un icono para iniciar sesión:

Logo de WordPress.com

Estás comentando usando tu cuenta de WordPress.com. Cerrar sesión / Cambiar )

Imagen de Twitter

Estás comentando usando tu cuenta de Twitter. Cerrar sesión / Cambiar )

Foto de Facebook

Estás comentando usando tu cuenta de Facebook. Cerrar sesión / Cambiar )

Google+ photo

Estás comentando usando tu cuenta de Google+. Cerrar sesión / Cambiar )

Conectando a %s