Page tree
Skip to end of metadata
Go to start of metadata

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

artifactID

magnolia-publishing-transactional-parent

Parent reactor.

magnolia-publishing-transactional-core

Extends functionality of the magnolia-publishing-core submodule.

magnolia-publishing-transactional-sender

Handles send operations to multiple public instances.

magnolia-publishing-transactional-receiver

Handles receive requests on multiple public instances.

magnolia-publishing-transactional-app

Extends the functionality of the magnolia-publishing-app submodule by adding the clean MgnlWorkspace function (only on public instance).

Installing

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

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

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

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

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

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

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.

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.