Migrating from Alfresco Enterprise to the Alfresco Community

We thought about downgrading Alfresco Enterprise 3.4.1 to the Alfresco community.

Im used for Alfresco Enterprise, but I have no experience with the community version.

Used EMC, Alfresco Explorer and own development based on web services API and Foundation API.

I was worried about database migration. Can I just configure Alfresco Community 3.4.e to use our Oracle database for Alfresco Enterprise 3.4.1? Is the scheme compatible for community and enterprise distributions? Which version of the Alfresco community should I use? 3.4.e? What is the downgrade path between distributions? Is there any correspondence between the versions of both distributions?

Any transition experience, guidance or any relevant information is appreciated.

+6
source share
5 answers

Alfresco Community Edition is open source and works with the open source stack. Your database options are PostGreSQL (recommended) or MySQL.

Alfresco Enterprise supports open source databases supported by the community, PostGreSQL and MySQL, as well as several proprietary databases. You can find more detailed information on the Database Configuration page . Oracle database support is available only in Enterprise.

Oracle , Alfresco . , , , Community uber!

, ​​ PostGreSQL MySQL, . Enterprise Service Packs (, 3.4.1) , ( Head). 3.4.x 3.4 , 3.4.x 4.x . , , ... Alfresco QA β†’ , β†’ , .

+8

Community Enterprise Oracle . Enterprise. Alfresco. Enterprise 3.4.2, .

+5

. : ", , ".

, X , .

, . , .

, ACP ?

+3

, . . Alfresco, , . , . , Alfresco Enterprise.

, , Alfresco.

+2

Alfresco . , 3.x , hibernate db. , Alfresco 3.4. 4.0 EE, postgres ( oracle, mysql) , , Alfresco Community 4.2.f ( API -). ( ), .

Here in Germany, it’s legally problematic to limit the use of the software in time if you sell a support subscription (at least for old contracts that you may have), so customers here can request support for an unlimited time license key EE, before terminating your subscription agreement. I recommend that you go this route and upgrade your old version 3.4 to the latest available corporate version 3.4.x or 4.x and stay on Oracle db if you don't care about these costs. This step should be done anyway ;-)

0
source

All Articles