Magnolia 5.4 reached end of life on November 15, 2018. This branch is no longer supported, see End-of-life policy.
The Activation module publishes content from an author instance to a public instance.
<dependency> <groupId>info.magnolia.activation</groupId> <artifactId>magnolia-module-activation</artifactId> <version>5.4.6</version> </dependency>
On the author instance, a
Syndicator collects the content that needs to be activated. It stores the content into an
ActivationContent object. The default
BaseSyndicatorImpl can activate content to any public instance that is configured as a subscriber. The configuration details of each subscriber are held in a
Subscriber Java bean at runtime. When you trigger an activation command, the syndicator creates an
ActivationContent object and sends it to each subscriber. There are two variations of
ActivationContent: current content and versioned content. In this context,
Content is defined by the filtering
Rule used to collect all the child nodes that are still considered to be part of the content for any given activation.
On the public instance, the Activation filter receives the content. The filter acts on the incoming request and saves the data into the repository.
Magnolia supports two methods of activating content
Activation is authenticated using public-key cryptography. See Activation security for more information.
The Activation module is configured in Configuration >
Users typically activate content by clicking Publish in the action bar. The click executes an
activate command which pushes the content from the author instance to subscriber instances. Conversely, when users click Unpublish the system executes a
deactivate command which deletes the content from public instances.
deactivate commands are configured in
default catalog contains commands which just publish the content without versioning. Magnolia also provides a
versioned command catalog. It contains identically named
deactivate commands which first version the content and then delegate to the default commands.
To use one of these commands, define the catalog and the command name in the action definition. See an example in Executing commands with actions.
activationLogStorage property defines where information about activations are logged. The default implementation MemoryActivationStorage keeps the information in memory.