Publishing Transactional module
Collaboration and workflow Bundled: DX Core
| Edition | DX Core |
|---|---|
License |
|
Issues |
|
Maven site |
|
Latest |
2.0.1 |
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).
|
Content publishing and content synchronization Always wait with content publishing actions until all content synchronization tasks have been finished. If you attempt to publish a page while the Synchronization module is mid-sync and hasn’t yet synchronized the page’s parent, the publishing process will fail. |
Module structure
The parent reactor’s artifactID is
magnolia-publishing-transactional-parent. 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 |
Installing with Maven
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>2.0.1</version> (1)
</dependency>| 1 | Should you need to specify the module version, do it using <version>. |
<dependency>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-transactional-sender</artifactId>
<version>2.0.1</version> (1)
</dependency>| 1 | Should you need to specify the module version, do it using <version>. |
<dependency>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-transactional-receiver</artifactId>
<version>2.0.1</version> (1)
</dependency>| 1 | Should you need to specify the module version, do it using <version>. |
<dependency>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-transactional-app</artifactId>
<version>2.0.1</version> (1)
</dependency>| 1 | Should you need to specify the module version, do it using <version>. |
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 publishing in such a 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.