Alfresco 1.3RC to 1.3 upgrade

[rafiton]

I was looking for a doc explaning how to upgrade from 1.3 Release Candidate to the GA 1.3 but to no avail.

help?

Rafi

[steve]

Hello,

During the development of 1.3 there have been several schema changes, and because it would prove very difficult for us to provide upgrade scripts for all the many variations of upgrading between 1.2.1, 1.3 beta, 1.3 Community Preview, 1.3 Release Candidate, 1.3 GA etc… we provide a script for the upgrade of a 1.2.1 to 1.3 GA install with the 1.3 GA release.

To upgrade one of the 1.3 releases prior to GA,  easiest way is by performing a full repository export of the old 1.3 release, then a full repository import into the 1.3 GA.

Steve

[rafiton]

Hi Steve,

I exported the entire repository (created 6 files) and installed 1.3 GA. When I try to import the files it says the files were uploaded successfuly but I do not see the repository but rather the files *.acp as files in the Company Home page.

Any idea?

Rafi

[steve]

Hi,

Did you follow the steps outlined in the Wiki?

http://wiki.alfresco.com/wiki/Export_and_Import#Web_Client_Export_.26_Import_of_a_Complete_Repositor...

Steve

[jarek_potiuk]

Success story BUT with some tweaking. We tried to do the export/import stuff from 1.3 dev (before RC) to final 1.3.0 and initially failed on  importing users (using http://wiki.alfresco.com/wiki/Export_and_Import#Web_Client_Export_.26_Import_of_a_Complete_Repositor...  procedure).
The error was:
10:49:32,655 DEBUG [repo.importer.ImporterBootstrap] Exception: org.alfresco.service.cmr.view.ImporterException: Failed to import package at line 1999; column 31 due to error: Association {http://www.alfresco.org/model/user/1.0}member is not valid for node {http://www.alfresco.org/model/system/1.0}container

After some investigation and experiments with 1.3.0 export we found out that  export schema for user changed. After unzipping export_users.acp we got in the .xml file:

<view:associations>
     <usr:member>
        <usr:authorityContainer view:childName="usr:GROUP_Administrators">
‍‍‍‍‍

Where 1.3.0 export contains:

..
<view:associations>
     <sys:children>
        <usr:authorityContainer view:childName="usr:GROUP_Administrators">
..
‍‍‍‍‍‍‍

After we changed this and closing tag in export_users.xml (and added back to .acp) - it worked fine.

[rafiton]

I have to admit that the import process seemed so complex that I decided to install and upload all the documents manually.

Given that the CIFS authentication problems I had in 1.3 RC are gone in 1.3 GA and that I kept the document library structure backed up on another computer it took me 2 secs to copy the docs

my 2 cents - if Alfresco is aimed at novice IT people (like MS Sharepoint is) I would recommend creating a simpler import process. I (as a user) really don't want to tweak xml files in order to import my data back. It sould be a much simpler process.

I have to admit that I really like Alfresco as software but it still needs some "productisation".

Cheers
Rafi Ton

[davidc]

You're correct that some administration tasks are more complicated than necessary (i.e. xml editing is required).  Simplification will come over time when we add more Administration UI.

However, I'd like to clarify that xml configuration is only required when exporting a complete repository and migrating it to a new installation.

It's possible for an end-user to export their spaces and files and re-import those into any other location whether same repository or another repository using simple clicks in the Web Client UI.