jpotts-alfresco-mbp:webapps jpotts$ pwd
/opt/apache/tomcat/apache-tomcat-6.0.32/webapps
jpotts-alfresco-mbp:webapps jpotts$ ls -la
total 16
drwxr-xr-x@ 9 jpotts admin 306 Feb 3 16:13 .
drwxr-xr-x 17 jpotts admin 578 May 27 2011 ..
drwxr-xr-x@ 13 jpotts admin 442 Sep 8 16:03 ROOT
lrwxr-xr-x 1 jpotts admin 54 Feb 3 16:13 alfresco -> /Users/jpotts/alfresco/webapps/alfresco-3.4d-community
drwxr-xr-x@ 45 jpotts admin 1530 Feb 2 2011 docs
drwxr-xr-x@ 6 jpotts admin 204 Feb 2 2011 examples
drwxr-xr-x@ 8 jpotts admin 272 Feb 2 2011 host-manager
drwxr-xr-x@ 9 jpotts admin 306 Feb 2 2011 manager
lrwxr-xr-x 1 jpotts admin 51 Feb 3 16:13 share -> /Users/jpotts/alfresco/webapps/share-3.4d-community

Jeff

thanks for the reply,

i create the folder alfresco4-0c in my webapps folder and i create alfresco folder and share folder in alfresco4-0c and extract the .war files, but i have the same error.

What’s wrong?

Thanks a lot

You should test Share with the same version of the Alfresco repository. So if you are testing Share 4.0.b it should be against Alfresco 4.0.b.

The safest/easiest way to run multiple instances of Alfresco is to:
1. Create a separate alf_data directory.
2. Create a separate database
3. Use separate tomcat instances or at least separate web applications

I have many different versions of Alfresco on my machine and I use a script to switch between them. This blog post talks about how that works. It was written a long time ago, but it all still applies. One big difference is that the properties file is now called alfresco-global.properties. That file is where you specify the data directory path, the database name, the database user, and the database password.

In your case you are upgrading so you’ll want to test your upgrade first. To do this, dump the database then tar up your alf_data directory. Then create a new database and load it with the dump you created. Create a new alf_data directory for your new version and un-tar the old data directory into it. Edit alfresco-global.properties to point to the test database and alf_data directory. DOUBLE CHECK THIS. You do NOT want to start up Alfresco with the new WARs on a test server and have them inadvertently point to the production database and data directory. If everything is set appropriately, drop the new alfresco.war and share.war files into a test tomcat instance and restart. This will give you a chance to test the upgrade including any customizations or extensions you may have made. (In fact, if you have made any, there will be the obvious step of merging those with the new configuration files which may have changed since the old version).

If everything tests out okay and you are ready to do this in production, all you have to do is shut down, merge the config and other customizations, drop in the new WARs, then restart.

Hope this helps,

Jeff

You need two WARs. The first one is alfresco.war. That contains the core repository and the Alfresco Explorer web client. The second is share.war. That contains only the Alfresco Share web client. I would extract alfresco.war into “alfresco” and share.war into “share”. If you extract alfresco.war into something different, you’ll have to do some Share configuration because it needs to communicate with the repository, and it expects the app to be called “alfresco”.

Jeff

i created alfresco-4.0c directory in my webapps folder, i extract the share.war manually, but when write this url: http://localhost:8081/alfresco-4.0c the browser response this message:

HTTP Status 404 – /alfresco-4.0c/

type Status report

message /alfresco-4.0c/

description The requested resource (/alfresco-4.0c/) is not available.

What’s wrong? Thanks a lot!

I’m a new to Alfresco and I recently purchased the Alfresco developers guide to help me understand the system.

My question is pertaining to upgrades. We are currently using a Tomcat installation on a BSD system and we’re running Alfresco version 3.4.c and we’re hoping to upgrade to the latest version.

In my tomcat/webapps folder I have /Alfresco and /Share. I downloaded and expanded Share 4.0b and was able to deploy the new Share instance in tomcat. So right now, I have the following:

/alfresco – version 3.4.c
/share – Production – version 3.4.c
/share4b – Testing new Share

How would I go about running multiple instances of the alfresco repository? I understand I must create a new mysql database, put the new information in the alfresco-global.properties file, specify a new alf_data directory as well.

How will the new ‘share4b’ site know to use the new repository? I apologize if my terminology or general idea of Alfresco is summit convoluted
but again, I’m starting from scratch and would like a better understanding of the upgrade procedures.

I appreciate any help you can provide. Excellent site, btw.

Jeff

I did choose really the worst solution to my problem!!!!

DO NOT RENAME WAR!

Thank you very much Jeff

If you put share-config-custom.xml in /WEB-INF/classes/alfresco/web-extension in your webapp instead of /shared/classes, you should be able to have a share-config-custom.xml that affects only a specific Share webapp.

Jeff