[DOCU-1735] Provide docs to upgrade from CE to EE Created: 18/Oct/18  Updated: 03/Oct/19  Resolved: 03/Oct/19

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1, 6.2

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Richard Gange
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Story Points: 13

 Description   

Provide docs to upgrade from CE to EE
https://documentation.magnolia-cms.com/display/DOCS62/How+to+upgrade+from+CE+to+DX+Core


Possible content:

  • Explain some general stuff, such as
    • You will need a license
    • There is EE Std. and EE Pro
    • You can do it
      • with Maven (preferred option)
      • or manually by copying around jar files
  • Provide a recipe
    • Maven based
      • Upgrade a preconfigured mgnl bundle
        • to EE STd.
        • to EE PRO
    • manually


 Comments   
Comment by Edwin Guilbert [ 18/Oct/18 ]

It should be also nice to list what features/modules users will gain by moving from community to enterprise bundles. It somehow will be clear with the maven artefacts and/or jars to be included in the war, but brief desc could be good too. Only for the ones included in the bundles, the list of all modules can be referenced anyways.

Describing functional differences between community and enterprise, like for example having more than one site definition, more than one theme, how different will look the configs, what they need to do to migrate their current configs. The possibility of workflows, new apps included, their purpose, etc

Comment by Edwin Guilbert [ 18/Oct/18 ]

Having this for 5.x would be preferable since most clients won't be using 6 for a while 

Comment by Christoph Meier [ 18/Oct/18 ]

Well, ebguilbert - what you ask in the comment above comes close to a list comparing CE, EE Std. and EE Pro

  • what once was removed from the corp. website (as decided by marketing) 
  • and what sales is always asking for 

A "conflict" where I want to stay neutral - or where I would ask stake holders and C-level managers first to take a decision whether we want to communicate such comparison list or not.

Comment by Edwin Guilbert [ 18/Oct/18 ]

I was worried i was going to give that impression, sorry. I still think its different from a list of features between different licenses.

 

My point is:

  • magnolia-community-demo-bundle

has physical differences to:

  • magnolia-enterprise-pro-demo-bundle

 

So listing the differences with a brief desc of the modules of the "delta set" I think would be useful. Its not a marketing/sales thing, its a maven artefacts technical comparison.

 

About this part: "having more than one site definition, more than one theme, how different will look the configs, what they need to do to migrate their current configs. "

I don't see the relation to any list comparison and it would be definitely needed by users since afaik project-related themes and site defs wont be moved automatically by version handlers (I could be wrong ofc).

Comment by Richard Gange [ 30/Sep/19 ]

ebguilbert and cmeier
So I finished a rough draft of this. It's here https://documentation.magnolia-cms.com/display/DOCS62/How+to+upgrade+from+CE+to+DX+Core. I would interested to get any feedback if you have some.

Explain some general stuff, such as
You will need a license
There is EE Std. and EE Pro

I did this for Magnolia 6 So Std/Pro don't apply for this version. I did mention the license in the description/introduction.

You can do it
with Maven (preferred option)
or manually by copying around jar files

I tried to cover both scenarios I have seen in practice. Of course Maven, but also for those that have deployed a pre-assembled bundle with added jars.

Provide a recipe
Maven based
Upgrade a preconfigured mgnl bundle
to EE STd.
to EE PRO
manually

What I tried to do was funnel everyone into a Maven based project. So I explain how to convert from manual to maven (automated war construction).

Additionally I added a section of moving from one DB to another.

Generated at Mon Feb 12 01:20:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.