just to chip in here, I've been trying to do an upgrade from 4.0.b to 4.0.d several times now, and finally managed to nail it:
My setup:
ubuntu 10.04 with postgresql 9.1 (using pitti PPA)
alfresco installed in /opt/alfresco (linked to /opt/alfresco-4.0.b), so I can configure things to point to /opt/alfresco and link/unlink when new versions are installed.
my production cluster uses different filesystems and SAN/NAS(NFS) systems for various directories namely the content store on NFS, and the SOLR indexes on local disks, with the postgresql database on a separate database server (the "simple" cluster model as explained in the alfresco wiki documentation), so I have to "mirror" and move various directories to different locations, like this:
dir.root=/opt/alf_data
=> required change in /opt/alfresco/tomcat/shared/classes/alfresco-global.properties
(basically I just moved /opt/alfresco/alf_data to /opt/alf_data; this is to setup a separate and isolated content store from the application installation directory, and ensure no overwrites on subsequent installs)
dir.keystore=/opt/alf_keystore
=> required change in /opt/alfresco/tomcat/shared/classes/alfresco-global.properties
=> required change in /opt/alfresco/tomcat/conf/server.xml
(basically I moved /opt/alfresco/alf_data/keystore to /opt/alf_keystore)
data.dir.root=/opt/alf_solr
=>required change in /opt/alf_solr/archive-SpacesStore/conf/solrcore.properties
=>required change in /opt/alf_solr/workspace-SpacesStore/conf/solrcore.properties
=> required change in /opt/alfresco/tomcat/conf/Catalina/localhost/solr.xml
(basically I moved /opt/alfresco/alf_data/solr to /opt/alf_solr; this is again to setup a separate and isolated index store from the application installation directory)
Finally, since this is an enterprise deployment, I have AD authentication to 3 different AD domains
=> required change in /opt/alfresco/tomcat/shared/classes/alfresco-global.properties
=> also required new subdirectories /opt/alfresco/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap-ad/ldap[123]/ and associated ldap-ad-authentication.properties file(s)
(those not used to unix regexp, the ldap[123] basically means I have three subdirectories ldap1, ldap2 and ldap3, to hold the different ldap-ad-authentication properties files which have the details for the three different AD servers)
So, what I did for the upgrade (final version, no errors in either alfresco startup, or solr execution):
1) stop alfresco
2) create a copy of the existing database (in case I need to rollback)
In production I would have backed up the database; in test/dev, I can afford to copy the database (makes it easy for me to rollback), so since I am using postgres and my existing database is called alfresco_cluster, su - postgres and run "createdb alfresco_cluster2 -O alfresco_c -T alfresco_cluster".
Henceforth I will use alfresco_cluster2 as the new DB
3) install alfresco 4.0.d, making sure to not install postgres, and use the new database from above
e.g. this is my test install, so
a) [jdbc
ostgresql://localhost/alfresco]: jdbcostgresql://localhost/alfresco_cluster2
b) Database name: [alfresco]: alfresco_cluster2
if I was doing this in production, my JDBC URL would look like jdbcostgresql://serverort/alfresco_cluster2
4) VERY IMPORTANT: at the end of the install, DO NOT start alfresco, i.e.
Launch Alfresco Community Share [Y/n]: N
5) now I need to redo my customizations; I chose to redo rather than copy the files over, so I could also manually check if 4.0.d has any new parameters in the config files I change.
a) relink /opt/alfresco to /opt/alfresco-4.0.d
b) I am of course keeping my previous /opt/alf_data content store directory, so I basically ignore the new /opt/alfresco/alf_data directory (except the solr directory, see later), and edit alfresco/tomcat/shared/classes/alfresco-global.properties to change dir.root (and others, see below)
c) as per above, I am reusing my old keystore, so edit both /opt/alfresco/tomcat/shared/classes/alfresco-global.properties and /opt/alfresco/tomcat/conf/server.xml to reflect the keystore change
d) for solr, I found out that there are some changes in solr in 4.0.d compared to 4.0.b, so if I reused the old solr store, even though I forced solr to rebuild the indexes by deleting /opt/alf_solr/workspace and /opt/alf_solr/archive, I would get errors in catalina.out like:
"SEVERE: org.alfresco.repo.search.impl.parsers.FTSQueryException: 03260000 line 1:97
mismatched input '.000' expecting TO ([@11,97:100='.000',<62>,1:97])
"
So I deleted (backed up) my old /opt/alf_solr directory, then moved /opt/alfresco/alf_data/solr to /opt/alf_solr, and as with above, edit the following files to reflect the change in directory for data.dir.root:
i) /opt/alf_solr/archive-SpacesStore/conf/solrcore.properties
ii) /opt/alf_solr/workspace-SpacesStore/conf/solrcore.properties
iii) /opt/alfresco/tomcat/conf/Catalina/localhost/solr.xml
e) for my AD authentication to 3 different AD domains
I just copied the previous /opt/alfresco-4.0.b/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap-ad/ldap[123]/ and associated ldap-ad-authentication.properties file(s) over to the new /opt/alfresco/… directories
Now, you can finally start alfresco, and check your /opt/alfresco/tomcat/logs/catalina.out and fingers crossed, like me, you won't have any errors related to the upgrade. Hope this helps!
My setup:
ubuntu 10.04 with postgresql 9.1 (using pitti PPA)
alfresco installed in /opt/alfresco (linked to /opt/alfresco-4.0.b), so I can configure things to point to /opt/alfresco and link/unlink when new versions are installed.
my production cluster uses different filesystems and SAN/NAS(NFS) systems for various directories namely the content store on NFS, and the SOLR indexes on local disks, with the postgresql database on a separate database server (the "simple" cluster model as explained in the alfresco wiki documentation), so I have to "mirror" and move various directories to different locations, like this:
dir.root=/opt/alf_data
=> required change in /opt/alfresco/tomcat/shared/classes/alfresco-global.properties
(basically I just moved /opt/alfresco/alf_data to /opt/alf_data; this is to setup a separate and isolated content store from the application installation directory, and ensure no overwrites on subsequent installs)
dir.keystore=/opt/alf_keystore
=> required change in /opt/alfresco/tomcat/shared/classes/alfresco-global.properties
=> required change in /opt/alfresco/tomcat/conf/server.xml
(basically I moved /opt/alfresco/alf_data/keystore to /opt/alf_keystore)
data.dir.root=/opt/alf_solr
=>required change in /opt/alf_solr/archive-SpacesStore/conf/solrcore.properties
=>required change in /opt/alf_solr/workspace-SpacesStore/conf/solrcore.properties
=> required change in /opt/alfresco/tomcat/conf/Catalina/localhost/solr.xml
(basically I moved /opt/alfresco/alf_data/solr to /opt/alf_solr; this is again to setup a separate and isolated index store from the application installation directory)
Finally, since this is an enterprise deployment, I have AD authentication to 3 different AD domains
=> required change in /opt/alfresco/tomcat/shared/classes/alfresco-global.properties
=> also required new subdirectories /opt/alfresco/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap-ad/ldap[123]/ and associated ldap-ad-authentication.properties file(s)
(those not used to unix regexp, the ldap[123] basically means I have three subdirectories ldap1, ldap2 and ldap3, to hold the different ldap-ad-authentication properties files which have the details for the three different AD servers)
So, what I did for the upgrade (final version, no errors in either alfresco startup, or solr execution):
1) stop alfresco
2) create a copy of the existing database (in case I need to rollback)
In production I would have backed up the database; in test/dev, I can afford to copy the database (makes it easy for me to rollback), so since I am using postgres and my existing database is called alfresco_cluster, su - postgres and run "createdb alfresco_cluster2 -O alfresco_c -T alfresco_cluster".
Henceforth I will use alfresco_cluster2 as the new DB
3) install alfresco 4.0.d, making sure to not install postgres, and use the new database from above
e.g. this is my test install, so
a) [jdbc
ostgresql://localhost/alfresco]: jdbcostgresql://localhost/alfresco_cluster2b) Database name: [alfresco]: alfresco_cluster2
if I was doing this in production, my JDBC URL would look like jdbc
ostgresql://serverort/alfresco_cluster24) VERY IMPORTANT: at the end of the install, DO NOT start alfresco, i.e.
Launch Alfresco Community Share [Y/n]: N
5) now I need to redo my customizations; I chose to redo rather than copy the files over, so I could also manually check if 4.0.d has any new parameters in the config files I change.
a) relink /opt/alfresco to /opt/alfresco-4.0.d
b) I am of course keeping my previous /opt/alf_data content store directory, so I basically ignore the new /opt/alfresco/alf_data directory (except the solr directory, see later), and edit alfresco/tomcat/shared/classes/alfresco-global.properties to change dir.root (and others, see below)
c) as per above, I am reusing my old keystore, so edit both /opt/alfresco/tomcat/shared/classes/alfresco-global.properties and /opt/alfresco/tomcat/conf/server.xml to reflect the keystore change
d) for solr, I found out that there are some changes in solr in 4.0.d compared to 4.0.b, so if I reused the old solr store, even though I forced solr to rebuild the indexes by deleting /opt/alf_solr/workspace and /opt/alf_solr/archive, I would get errors in catalina.out like:
"SEVERE: org.alfresco.repo.search.impl.parsers.FTSQueryException: 03260000 line 1:97
mismatched input '.000' expecting TO ([@11,97:100='.000',<62>,1:97])
"
So I deleted (backed up) my old /opt/alf_solr directory, then moved /opt/alfresco/alf_data/solr to /opt/alf_solr, and as with above, edit the following files to reflect the change in directory for data.dir.root:
i) /opt/alf_solr/archive-SpacesStore/conf/solrcore.properties
ii) /opt/alf_solr/workspace-SpacesStore/conf/solrcore.properties
iii) /opt/alfresco/tomcat/conf/Catalina/localhost/solr.xml
e) for my AD authentication to 3 different AD domains
I just copied the previous /opt/alfresco-4.0.b/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap-ad/ldap[123]/ and associated ldap-ad-authentication.properties file(s) over to the new /opt/alfresco/… directories
Now, you can finally start alfresco, and check your /opt/alfresco/tomcat/logs/catalina.out and fingers crossed, like me, you won't have any errors related to the upgrade. Hope this helps!
