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.
The Publishing Transactional module ensures synchronization of content between multiple public instances. The module extends the single-receiver, Community Edition's Publishing module by providing parallel publishing to up to 10 receivers (public instances).
The parent reactor's artifactID is
. The module consists of the following submodules:
|Extends functionality of the |
|Handles send operations to multiple public instances.|
|Handles receive requests on multiple public instances.|
|Extends the functionality of the |
<dependency> <groupId>info.magnolia.publishing</groupId> <artifactId>magnolia-publishing-transactional-core</artifactId> <version>1.2.4</version> </dependency>
<dependency> <groupId>info.magnolia.publishing</groupId> <artifactId>magnolia-publishing-transactional-sender</artifactId> <version>1.2.4</version> </dependency>
<dependency> <groupId>info.magnolia.publishing</groupId> <artifactId>magnolia-publishing-transactional-receiver</artifactId> <version>1.2.4</version> </dependency>
<dependency> <groupId>info.magnolia.publishing</groupId> <artifactId>magnolia-publishing-transactional-app</artifactId> <version>1.2.4</version> </dependency>
Content is published transactionally automatically when the Publishing Transactional module is installed. No configuration is required.
Publishing content to all receivers in a single transaction means that if one of the public instances is down, content will not be published to any of them. The user is notified of the situation in an error message. To resume publilshing in such case, an administrator has to either bring the affected receiver back online, disable it, or remove it from the list of receivers. When they later enable such a receiver, it is strongly recommended to completely republish all content to the affected receiver.
Transactional publishing works the same way also for unpublishing and the same way whether invoked directly or via an approval workflow.
While it is possible to have more than 10 receivers (public instances), the module can only publish content to up to 10 receivers in parallel.