Page tree

Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.

Since Magnolia 5.6, the Transactional Activation module has been deprecated in favor of the Publishing Transactional module.

The Transactional Activation module ensures synchronization of content between multiple public instances. The module extends the single-subscriber, Community Edition's Activation module by providing parallel publishing to up to 10 public instances. 

Publishing to multiple subscribers is encapsulated in a single transaction. This means that if one of the public instances is down, content will not be published to any of them. 

Installing

Maven is the easiest way to install the module. Add the following to your bundle:

<dependency>
  <groupId>info.magnolia</groupId>
  <artifactId>magnolia-module-exchange-transactional</artifactId>
  <version>2.5</version>
</dependency>

Pre-built JARs are also available for download. See Installing a module for help.

Usage

Content is activated (published) transactionally automatically when the Transactional Activation module is installed. No configuration is required.

Activating content to all subscribers in a single transaction means that if one of the public instances is down, content will not be activated to any of them. The user is notified of the situation in an error message. To resume activation in such a case, an administrator has to either bring the affected subscriber back online, disable it, or remove it from the list of subscribers. When they later enable such a subscriber, it is strongly recommended to completely republish all content to the affected subscriber.

Transactional activation (publishing) works the same way for deactivation (unpublishing) and the same way whether invoked directly or via an approval workflow.

While it is possible to have more than 10 subscribers (public instances), the Transactional Activation module can only publish content to up to 10 subscribers in parallel.