Publishing Transactional module

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).

Module structure

The parent reactor's artifactID is  magnolia-publishing-transactional-parent  . The module consists of the following submodules:

Installing

<dependency>
  <groupId>info.magnolia.publishing</groupId>
  <artifactId>magnolia-publishing-transactional-core</artifactId>
</dependency>

<dependency>
  <groupId>info.magnolia.publishing</groupId>
  <artifactId>magnolia-publishing-transactional-sender</artifactId>
</dependency>

<dependency>
  <groupId>info.magnolia.publishing</groupId>
  <artifactId>magnolia-publishing-transactional-receiver</artifactId>
</dependency>

<dependency>
  <groupId>info.magnolia.publishing</groupId>
  <artifactId>magnolia-publishing-transactional-app</artifactId>
</dependency>

Usage

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.