How to Schedule the Activation and Deactivation of Pages in AEM | AEM Community Blog Seeding

[#1]

How to Schedule the Activation and Deactivation of Pages in AEM by Mohan Giradkar

Abstract

Introduction to AEM
Adobe Experience Manager is a content management system tool developed by Adobe. A content management system tool is used for website authoring, collaboration, and administration which ultimately helps to create, edit and publish the content. Using the AEM tool, creating websites, mobile apps, or forms is simple. AEM is a business content management system (CMS) that optimizes authoring and content management.



Basics of AEM
The author instance, publish instance, and dispatcher form the core of the entire AEM configuration according to the AEM architecture.

Author
In simple terms, an Author instance is where users create and edit the content, which can be published when the activation is performed. The author allows for complete authoring, component configuration, uploading, modification, deletion, and related tasks. Activation is done for content that needs to be live or be made public, and deactivation is done for content that needs to be removed. In short, the author instance decides which content must be released.

Publisher
Publish instances and author instances are similar, except for authoring capabilities. The publish instance or publisher is where published content resides. The content activated on the author is replicated on the publisher, making the publisher’s version of the activated content public.

Dispatcher
The dispatcher helps in caching certain pages and assets. Caching helps to speed up the delivery of the content to the end user; disallowing cache to specific pages/paths can also be done for security purposes. Due to its load balancing capabilities, the dispatcher acts as a load balancer to various publishers, which makes the response time faster.

Read Full Blog

How to Schedule the Activation and Deactivation of Pages in AEM

Q&A

Please use this thread to ask the related questions.

[#2]

Good information, but one piece of feedback though, the author should use touch UI interfaces instead of classic UI.