Publishing and activation

On the surface, both publishing and activation, that is their modules and associated apps serve the same purpose: publish content from an author instance to a public instance:

Nevertheless, the internals of this process are different:

• Activation is an older implementation inherited from the 5.5 branch. Activation can still be used in the 5.6 branch, but it is structurally and also partly functionally inferior to the newer publishing implementation.
  For more information about Activation please read: 
  
  
  • Activation overview
  • Activation module
  • Transactional Activation module
  • Activation Tools app
  • Activation security
  • Activation errors
    
    
• Publishing is a refactored version of activation. The original Activation module has been broken into multiple Publishing submodules. The driving decision was to have a set of maintainable and extensible components. Another reason was to remove deprecated code. The core activation concepts remain the same. Despite the transport layer is still using the HTTP protocol, publishing allows to easily plug in any type of transport layer.
  For more information about publishing please read: 
  
  
  • Publishing overview
  • Publishing module
  • Publishing Transactional module
  • Publishing Tools app
  • Activation security
  • Activation errors

Replacing activation with publishing

The bundles in the 5.6 branch are shipped with publishing by default. If you are migrating from a pre-5.6 branch and intend to replace activation with publishing, see the Publishing vs Activation and custom commands section on the Upgrading to Magnolia 5.6.x page.