Magnolia Author - public instance sync process

Magnolia Author instance-

To sync Magnolia author and public instance, first we have to ensure author and public nodes know each other.

As shown in the below image, under configuration menu, please click on the subscribers link. It will lead you to subscriber node. Give your public http URL in the url field.

Please make sure the subscriptions node present under subscribers. It will hold what can kind of information to be transported across these nodes.

Activation tolerance

There is no gurantee both author and public instances should have been started in the same time (time sync). Magnolia expects the time sync between the author and public instances. To bridge this delay, we have this settings configuration --> module --> exchange-simple --> activationDelayTolerance

Key generation and sync

After doing the above steps, still magnolia will try to match their activaton keys before sync. We can generate and update the activation key. You have to update the generated activation key (generated in author) into public instance

Key updation

Now you can start publishing the content from author to public

Magnolia CMS - Introduction

What is Magnolia CMS?

Magnolia CMS is an open-source Web Content Management System that focuses on providing an intuitive user experience in an enterprise-scale system. Its combination of ease-of-use and a flexible, standards-based Java architecture has attracted enterprise customers.

Magnolia CMS is not a framework to build web applications, like JSF or Struts. However, Magnolia CMS can be used to manage data. You can for instance manage products and use them as content for Web pages.
Author and Public Instances

Magnolia CMS is distributed as two web-applications, one acting as the authoring instance and the other as the public environment. This allows for better security, having one application inside your firewall and one outside. It also enables clustering configurations.
Author instance is where all authors work. It typically resides in a secure location such as behind a corporate firewall, inaccessible from the Internet. The author instance publishes content to public instances.

Public instance receives the public content and exposes it to visitors on the Web. It resides in a public, reachable location. You can have more than one public instances, serving the same or different content.