nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Migration from alfresco 2.1 to alfresco 3.1

kirit

Hello,
We want to migrate from alfresco 2.1 to alfresco 3.1.
So if anybody has done this wanted to know the major changes in DM side.
is there any compatibility issues with 3.1?
We have gone through the general migration steps provided in Wiki, apart from that is there anything needs to be taken care?

Find more posts tagged with

Comments

jarrett

I've done this and it went smoothly. I did do a trial upgrade first to make sure things would work first.

The release notes for each version are a great resource to learn what has changed between versions. The only changes your end users will notice is a few icons have changed in the actions menu.

If you are at 2.1 you will need to get back on a supported upgrade path. Getting back on a supported upgrade path was the most painful part of the process because upgrade do take awhile to complete so going through two of them can be very time consuming.

The supported upgrade paths are:
    * Version 2.1.5 to Version 3.0
    * Version 2.1.5 to Version 2.2.1 to Version 3.0
    * Version 2.2.0 to Version 2.2.1 to Version 3.0
    * Version 2.2.1 to Version 3.0
    * Version 2.1.6 to Version 3.0 (SP1)
    * Version 2.1.6 to Version 2.2.2 to Version 3.0 (SP1)
    * Version 2.2.0 to Version 2.2.2 to Version 3.0 (SP1)
    * Version 2.1.7 to Version 3.1
    * Version 2.2.3 to Version 3.1
    * Version 3.0 to Version 3.1
    * Version 3.0 SP1 to Version 3.1

Just remember backups are your friends, very good friends. One thing that I recommend doing is changing the JAVA_OPTS in alfresco.sh/alfresco.bat to those you plan to use once your new installation is in place. I found the out of the box settings to be very low for the resources are server had available. These low setting could have really prolonged our content migration.

kirit

Thank you jarrett,
As we are at 2.1 we will have following choices:

1) 2.1 to Version 2.1.7 to Version 3.1
2) 2.1 to Version 2.2.3 to Version 3.1
3) 2.1 to Version 2.2.1 to Version 3.0 to Version 3.1

Repository migration will not be a big issue. but what the problem here would be is fitting the code with new SDK,
so it will be costly operation by time to compile custom code in each version migration.
so wanted to know in which version we have major code/API/Library changes in DM side.

Thnaks.