Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Magnolia Transactional Activation module ensures synchronization of content between multiple public instances during publishing. The module extends the Exchange Simple module delivered with the Community Edition and features parallel activation to up to 10 public instances at once and synchronization of content between all subscribed public instances by encapsulating activation to all subscribers in single transaction.
Transactional Activation is an enterprise module, packaged as
magnolia-module-exchange-transactional.jar, and typically already installed. Go to Magnolia Store - Installed modules in AdminCentral to check. To install the module individually, see the general module installation instructions.
See the general module uninstalling instructions and advice.
Transactional activation is automatically used when the module is installed and no configuration is required. However, doing the whole activation in a single transaction means that if one of the public servers is down, content cannot be activated and the user will be informed of the situation in an error message. To resume activation in such case, an administrator has to either ensure that the affected public server is back online, or disabled or removed from the list of subscribers. When you re-enable such a subscriber, it is strongly recommended to do a complete reactivation of all content to the affected subscriber.
The functionality works the same way for both activation and deactivation, irrespective of how the activation is invoked (direct activation or via workflow).
More details about the implementation and workings of the module can be found at Jan's blog Magnolia's New Transactional Activation Module.